去读这篇论文。然后再读他的书《数据库管理的关系模型》（The Relational Model for Database Management）：https://codeblab.com/wp-content/uploads/2009/12/rmdb-codd.pd.... 他对数据管理的预见之超前、之精准，简直令人叹为观止。作为当年不幸学了……
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…
…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.
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…
摘自维基百科：正是在此时，埃德·奥茨[4]向迈纳和埃里森推荐了一篇关于数据库管理关系模型的 E. F. Codd 论文。然而它引用的 PDF 里却说是埃里森干的。我觉得这种事儿恐怕永远都不会有定论，因为每个人的回忆总会有那么一点出入。这并不……
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…
…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…
…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…
去读这篇论文。然后再读他的书《数据库管理的关系模型》（The Relational Model for Database Management）：https://codeblab.com/wp-content/uploads/2009/12/rmdb-codd.pd.... 他对数据管理的预见之超前、之精准，简直令人叹为观止。作为当年不幸学了……
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…
……对我有点价值的东西），而且在边做东西边遇到问题时，翻书来找答案实在太慢了。对于我感兴趣的领域，我偶尔确实喜欢读一读“具有历史意义”的编程书（比如 Codd 的《数据库管理的关系模型》），但我极少会从头到尾完整读完一本书。
…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.
我自己不用数据库，但过去几周关于“NoSQL”的讨论勾起了我的好奇心，刚好手头有一本 Codd 的《数据库管理的关系模型》，我就一直在抽空翻读，目前主要感兴趣的是理论部分。他花了大量篇幅抱怨根本没有哪家供应商真正做出了哪怕稍微接近……的数据库。
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…
摘自维基百科：正是在此时，埃德·奥茨[4]向迈纳和埃里森推荐了一篇关于数据库管理关系模型的 E. F. Codd 论文。然而它引用的 PDF 里却说是埃里森干的。我觉得这种事儿恐怕永远都不会有定论，因为每个人的回忆总会有那么一点出入。这并不……
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…
……能完美且全面地表征它们的业务领域。这根本不现实。光是对单一文化背景下的姓名和地址进行解析就难搞得要命。其次，Codd 后期最重要的著作《数据库管理的关系模型》中，包含了要被认定为关系型 DBMS 所必须满足的“十二条法则”（编号为 0 到 12）[0]。其中第 3 条法则是： > 法则 3：空值的系统化处理： > 空值……
…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…
……我没填，但我依然是有名字的。不能因为某个值在你的数据库里是未知的，就代表它未被定义。E. F. Codd 就思考过这个问题。[0] > Codd 在他1990年出版的《数据库管理的关系模型：第二版》中指出，SQL 标准强制规定的单一 Null 是不够用的，应该替换为两种独立的 Null 类型标记，用以说明数据缺失的具体原因。在 Codd 的书里，这两种 Null 类型……
…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…