First, we should note that SQL and relational model in general were designed long time ago to interact with the end user. This user-oriented nature had vast implications: […] No one can expect human users to explicitly control concurrency, integrity, consistency, or data types validity. That’s why SQL pays a lot of attention to transactional guaranties, schemas, and referential integrity.
I had always wondered about that, and it never occurred to me that SQL could have been designed primarily for end users. So it does make sense that, when accessing my database from PHP, I feel no need to use stuff like foreign keys constraints in the schema itself, for instance.
(Can’t vouch for the rest of the article, still haven’t read it. It’s long, and I have to be in a more open and productive state of mind to appreciate what it’s offering.)
Want to know when I post new content to my blog? It's a simple as registering for free to an RSS aggregator (Feedly, NewsBlur, Inoreader, …) and adding www.ff00aa.com to your feeds (or www.garoo.net if you want to subscribe to all my topics). We don't need newsletters, and we don't need Twitter; RSS still exists.
Legal information: This blog is hosted par OVH, 2 rue Kellermann, 59100 Roubaix, France, www.ovhcloud.com.
Personal data about this blog's readers are not used nor transmitted to third-parties. Comment authors can request their deletion by e-mail.
All contents © the author or quoted under fair use.
