ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

The Relational Model and Graph Databases

Neo4J is still a relational database. […] Relationships are also first-class citizens in graph databases, and in some cases are your focus.

rpocklin.wordpress.com

Many are confusing the relational model for relationships between entities. In the paper “A Relational Model of Data for Large Shared Data Banks”, E.F.Codd writes:

The term relation is used here in its accepted mathematical sense. Given sets S1, , … , Sn, (not necessarily distinct), R is a relation on these n sets if it is a set of n-tuples each of which has its first element from S1, its second element from S2, and so on.’ […] More concisely, R is a subset of the Cartesian product S1X S2XX Sn

Codd’s paper is only 11 pages long, so if you haven’t checked it in a while, maybe it is time to do so.

The relational view (or model) of data described in Section 1 appears to be superior in several respects to the graph or network model presently in vogue for non-inferential systems.

This was written in 1970 and things are changing again.

Original title and link: The Relational Model and Graph Databases (NoSQL databases © myNoSQL)