Working on a book of 2000-2006 material from the old dbdebunk.com, I came across the following 10/29/04 exchange. MySQL has probably improved--although, adding features post-hoc to products that were not explicitly designed for such upgrading is always problematic--more complex and limited than necessary. However, education and foundation knowledge have become worse and, from a foundational perspective, so have products and practices.
JG: fell asleep dreaming of column constraints. I woke up thinking of foreign keys. I've been married to MySQL for so long that I had no idea all of these other things were possible!
Using a database and not knowing about foreign keys? My immediate reaction was to be astounded. However, he just happens to have begun with the least-robust database product on the market, and his learning is (evidently) confined to whatever product he happens to be using.
Astounded? Nah, standard operating procedure.
1. Quote of the Week
In this paper we briefly review some of these issues and then concentrate on the problem of generalizing the formal framework of the relational data model to include null values. A basic problem with null values is that they have many plausible interpretations.
--Database Relations with Null Values, Bell Labs, 1983
No, that's not the basic problem.
2. To Laugh or Cry?
Relational table naming convention
3. Online Debunkings
4. Interesting Elsewhere
5. And now for something completely different
My May post @All Analytics.
I’ve often expressed skepticism here and elsewhere about “data science”
as currently used and hyped. Science is about development, testing, and
application of theories. Data science is about general theories of data.
For example, "relational theory" is the application of logic and set
theory to database management to guarantee provably logically correct
data analysis results, yet it is absent from the list of desirable
skills for “data scientists”.
Read it all. (Please comment there, not here)
I have just posted descriptions of all new versions of all six papers in the PRACTICAL DATABASE FOUNDATIONS Series:
#1: Business Modeling for Database Design
#2: The Costly Illusion: Normalization, Integrity and Performance
#3: The Last NULL in the Coffin: A Relational Solution to Missing Data
#4: The Key to Keys: A Matter of Identity
#5: Truly Relational: What It Really Means
#6: Domains: The Database Glue
The changes are significant and there are a few error corrections.
Since these are new versions, not revisions, the following applies:
- Those who ordered in 2015 get free copies.
- Those who ordered in 2014 get a 50% discount.
Please email me with proof of purchase.
For more details and how to order see PAPERS page.
1. Quote of the Week
He started his SQL Server career when he debuted as an accidental DBA in 2005. Seeing Reporting Services 2005 demoed for the first time sealed the deal, and it has been all data ever since, leaving the worlds of networking and systems admin behind. After being a full-time dev/operational DBA with everything since SQL 2000, he is now back to BI, as a Senior BI Engineer/Consultant. --Online Bio
2. To Laugh or Cry?
3. Online Debunkings
4. Interesting Elsewhere
Obfuscated SQL Contest Winners!
H/t Todd Everett.
5. And now for something completely different
In a LinkedIn thread that followed my Comments On Stonebraker Interview, Erwin Smout mentioned David Maier's 1991 critique of the 1990 Third Generation Data Base System Manifesto (3GM), of which Stonebraker was one of the authors. I was aware of the 3GM, of course, but had not read it because, at the time, it did not benefit from favorable reviews. I considered The Third Manifesto by Date and Darwen more significant, in part because it was authored by relational experts and because it was backed up by a proposed fully computational language with a fully relational component. But when Erwin mentioned Maier's piece, I asked him if he had a copy and he found a scanned PDF copy online.
Having not read the 3GM, I am not in a position to comment on Maier's critique thereof, but I would like to comment on the general topics in his Preliminaries that attracted my attention.
Housekeeping: I have added the following:
1. Quote of the Week
I am new to this domain. Please guide me to choose which database to choose among the NOSQL databases. Also which OS the database supports and how to add data to the database(which language). The requirement is to store pictures and alpha numeric s in database. A web server would be designed to extract data from the database and display in web application. The important requirement is scalability so I explored and found that NoSQL database will best fit the requirement. --LinkedIn.com
CJ Date calls this "I don't know how to do my job and am looking for somebody to do it for me."
2. To Laugh or Cry?
Docbase, Graphbase, Colubase, Triplestore ,which better fo RDF triples
3. Online Debunkings
4. Interesting Elsewhere
5. And now for something completely different
