5 ms·
Yes, this is roughly what I was getting at. Relations are sets of sets, and the relationships are products of the query method, not a static property of the st
by cmrdporcupine 6y ago
Yes, this is roughly what I was getting at.
Relations are sets of sets, and the relationships are products of the query method, not a static property of the storage of the data. This insight by Date and Codd was a huge discovery in data management.
Unfortunately SQL tended to paper over some of this beauty with its talk about "tables" with "columns", which are just one way of representing relation and tuples. I can't count the number of times I've heard someone say "but my data doesn't fit into a table", completely not getting it.
That combined with the rapid rise in object-oriented programming through the 90s and early 2000s, as well as a bunch of other things I won't get into, led to many people mistreating and/or rejecting the relational database.
We were taught, or taught ourselves to model our applications in an object-oriented way, and then became frustrated because we treated the database as a "datastore" rather than an information modeling and retrieval tool like it was meant.
Without an understanding of relational fundamentals people repeated the same mistakes that Date and Codd were originally trying to rectify with their pioneering work on the relational database. The relational model was a response to the problems with hierarchical and network databases; to try and formalize a more flexible model, with a mathematical and logical basis.
"Graph databases" and "document databases" and "object databases" _look_ more flexible from the front, but fundamentally are the opposite. They confine the kinds of relationships data can take, in advance.
The object oriented model is good for representing some aspects of our world; especially, perhaps, graphical interfaces, or simulation systems. In my opinion it is inferior for the modeling of data/information itself.
We need a relational renaissance.