ErwinSmout

9 ms·

1. 61.▲
   by ErwinSmout 8y ago

   Which is the reason why you shouldn't write outer joins.
2. 62.▲
   by ErwinSmout 10y ago

   My DBMS is sufficiently expressive, thank you.
3. 63.▲
   by ErwinSmout 10y ago

   Placing this in its context of things said previously, "The DBMS doesn't read your mind before interpreting relations.", "Which is why the real interpretation happens outside the DBMS.", "Unfortunately, compute
4. 64.▲
   by ErwinSmout 10y ago

   I thought it was the database designer. But OK, maybe that's just semantics and I'm not very good at those.
5. 65.▲
   by ErwinSmout 10y ago

   The DBMS doesn't read your mind before interpreting relations. Which is why the real interpretation happens outside the DBMS. And which is also why the DBMS needs "help" from its users when deciding whether TUPLE{} represents
6. 66.▲
   by ErwinSmout 10y ago

   "If two relations have identical designs, the difference can only be encoded in the relation (and possibly attribute) names," True, though the (and possibly attribute names) part seems dubious to say the least. Different attribut
7. 67.▲
   by ErwinSmout 10y ago

   No, the real meaning of a relation is the intended interpretation it was given when it was designed (and which is also the criterion by which the database user decides whether a tuple should be present or not, thus by which the database use