The difficulty with caring about ordering in the relational model is that suddenly you're imposing a lot more constraints: when you're joining two tables, whose order 'wins'? If you say (for example) that left side wins, you then need to keep track of that order through your query.
EMPLOYEE(Daniel Smith, Marketing) → TRUE
EMPLOYEE(Jebediah Vargas, Marketing) → FALSE
However, if the employee name in the function is not Daniel Smith but the employee is in marketing, the first predicate is true. How does that fit into relational databases?P.S. Great article!
In terms of tables, the rows are exactly the subset of predicates that are TRUE. So FALSE statements like the second one are indicated by their absence in the employee table.
Strictly speaking, the relations of database theory are different objects, but closely related. (Yes, I just made an awesome pun.)
I'm surprised that the author didn't include "a relation is a set of tuples" as a definition in the article. Also, absolutely nothing is said about viewing a relation as a graph.
Sorry, had to chime in with that