From: http://www.json.org/
JSON (JavaScript Object Notation) is a lightweight data-interchange
format. It is easy for humans to read and write. It is easy for
machines to parse and generate. It is based on a subset of the

http://www.nou.edu.ng/noun/NOUN_OCL/pdf/pdf2/MBA%20758%20Database%20Management%2
0System.pdf
"IBM started working on a prototype system loosely based on Codd's
concepts as System R in the early 1970s — unfortunately, System R
was conceived as a way of proving Codd's ideas ...

One I can't seem to find is:
E. F. CODD, "Recent Investigations in Relational Database Systems," IBM.
Research Report RJ1385
Grateful if anybody can point to a free link or even send it privately

I recently bumped into two patterns in schema design which I found
interesting, especially since they seem to imply a real use for
disjoint union types/domains and/or surrogate keys in schema design.
Since that sort of thing is bound to be controversial, I thought I

In his 'Writings' series, this time from the 2006 edition, chapter 13,
'More on Normalization', Date examines a suggestion by one his
correspondents, known only as 'ADR'.  This suggestion intrigued me,
here's a longish quote for some context:

I can't remember where in his papers Codd stated the Information
Principle but here's a version of a quote by Date: "The entire
information content of a relational database is represented in one and
only one way: namely, as attribute values within tuples within relations."

I'm trying to understand the relationship between referential
integrity and foreign key constraints. My example is suppose we
have the ubiquitous supplier who sends the usual Orders with
the usual info but also includes a Coupon that can be redeemed

I'm trying to implement a tree structure, hence I'd like the Nested
Set model, but I need to be able to record the history of the tree
structure *somehow* so that I can access previous versions.
I've searched up and down online but all I can find are transactions