Aheo asks if there is ok for a single column table . How about one without columns, or given that it seems difficult for most modern "relational" DBMSs, a relationship without attributes?
DEE and the Cartesian product form a monoid. In practice, if you have a relational date representation operator, you should use DEE as a grouping relation to get totals. There are many other examples where DEE is practically useful, for example. in a functional setting with a binary join operator you get n-ary join = foldr join dee
- , . , , . ( UNIQUE , , ... ).
UNIQUE
blazes , ( ) - , ?!
: . " " , "" "" () TABLE_DEE TABLE_DUM ().
TABLE_DEE
TABLE_DUM
, , , 1 0 .
" : . " "Date Darwen () TABLE_DEE TABLE_DUM ().
, , , 1 0 ".
, , "TRUE" "FALSE" . , , , " " " ", .
, " IF/ELSE": TABLE_DUM - , to TABLE_DEE . , R relvar S, TABLE_DEE TABLE_DUM, RA " S R else FI", FI .
Hm. " ", . , , !
cjs=> CREATE TABLE D (); CREATE TABLE cjs=> SELECT COUNT (*) FROM D; count ------- 0 (1 row) cjs=> INSERT INTO D () VALUES (); ERROR: syntax error at or near ")" LINE 1: INSERT INTO D () VALUES ();
. , , , . , .
TABLE_DEE TABLE_DUM SQL. , , db .
It is also difficult to see the usefulness of TABLE_DEE and TABLE_DUM in relational algebra. Need to look beyond that. To get an idea of how these constants can come to life, consider a relational algebra placed in the proper mathematical form, which is as close as possible for Boolean algebra. D & D Algebra A is a step in that direction. Then we can express the classical operations of relational algebra in terms of more fundamental ones, and these two constants will become really convenient.