The relational model for database management
by E. F. Codd · first published 1990
7mentions
2recommended by
7HN commenters
2009–2025first – last mentioned
29% recommend71% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Read this paper. Then read his book, The Relational Model for Database Management: https://codeblab.com/wp-content/uploads/2009/12/rmdb-codd.pd.... It’s mind boggling how much he anticipated about data management, and was absolutely accurate about. As someone who unfortunately learned…
on “A Relational Model of Data for Large Shared Data Banks (1970) [pdf]” ↗…something of value to me), and books are too slow to go through questions I might have while building stuff. I do enjoy an ocassional "historical" programming book for a subject I care about (eg. Codds Relational Model for Database Management), but rarely will I read a book cover to cover.
on “Ask HN: As a developer, do you read Programming books?” ↗I don't use databases myself, but the discussions over the last few weeks about "no-SQL" have gotten me curious and I have been nibbling at Codd's "The Relational Model for Database Management" since I had it laying around, and it is mostly theory I am interested in right now. He spent a great deal of time complaining that no vendor actually produced a database that was at all close to the…
on “My Thoughts on NoSQL” ↗From wikipedia: It was at this time that Ed Oates[4] introduced Miner and Ellison to a paper by E. F. Codd on the relational model for database management. yet the PDF it references says ellison did it. i think this is one of those things that will always be up for debate, as everyone is going to have a slightly different recollection of it. it doesn't…
on “Why it pays to be a jerk (2011)” ↗…perfectly and comprehensively represent their domains. That's not realistic. Parsing Names and Addresses for even a single culture is notoriously difficult. Second of all, Codd's later major work, The Relational Model for Database Management, includes his Twelve Rules (numbered 0 to 12) for database design in order for a DBMS to be considered relational[0]. Rule number 3 is: > Rule 3: Systematic treatment of null values: > Null values…
on “NULL: The worst mistake of computer science? (2015)” ↗…I don’t fill in, I still have a name. Just because a value is not known by your database doesn’t mean it isn’t defined. E. F. Codd thought about this issue.[0] > Codd indicated in his 1990 book The Relational Model for Database Management, Version 2 that the single Null mandated by the SQL standard was inadequate, and should be replaced by two separate Null-type markers to indicate why data is missing. In Codd's book, these two Null-type…
on “SQL nulls are weird” ↗E. F. Codd - The Relational Model for Database Management - Version 2.
on “Important database news from the last few months” ↗