Follow @DBDebunk Follow @ThePostWest

1.
A new Quote of the Week was posted on the QUOTES page.
I contend that in a certain sense the perspective is upside down and backwards. Can you figure out why?

2.
A new To Laugh or Cry? item was posted on the LAUGH/CRY? page.

3.
My latest Data Fundamentals column and a thread I participated in were posted on the ONLINE page.

4.
From Erwin Smout (via email):

In 2009, the ACM re-published Codd's paper Derivability, redundancy and consistency of relations stored in large data banks.

For searching purposes, the ACM "classifies" each published article using some "taxonomy" of their own making. Apparently, Codd's paper is classified under "Database Administration" and not under "Relational Database Model".

Says a lot, doesn't it?

UPDATE: I was wondering what ACM did classify under "relational model" (you can probably guess what I suspected). So I asked Erwin to check and here's what he found:

(1)
ORDB holistic design - 2012
Patricia Roberts
Proceedings of the 16th International Database Engineering & Applications  Symposium

(2)
Integrating trust management and access control in data-intensive Web  applications - 2012
Sabrina De Capitani Di Vimercati, Sara Foresti, Sushil Jajodia, Stefano 
Paraboschi, Giuseppe Psaila, Pierangela Samarati
ACM Transactions on the Web (TWEB), Volume 6 Issue 2, May 2012

(3)
Query-based data pricing - 2012
Paraschos Koutris, Prasang Upadhyaya, Magdalena Balazinska, Bill Howe, Dan  Suciu
Proceedings of the 31st symposium on Principles of Database Systems

(4)
Worst-case optimal join algorithms: [extended abstract] - 2012
Hung Q. Ngo, Ely Porat, Christopher Ré, Atri Rudra
Proceedings of the 31st symposium on Principles of Database Systems

(5)
Efficient transaction processing in SAP HANA database: the end of a column store myth - 2012
Vishal Sikka, Franz Färber, Wolfgang Lehner, Sang Kyun Cha, Thomas Peh, Christof Bornhövd
Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data

(6)
Interactive performance monitoring of a composite OLTP and OLAP workload - 2012
Anja Bog, Kai Sachs, Hasso Plattner
Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data

(7)
Temporal alignment - 2012
Anton Dignös, Michael H. Böhlen, Johann Gamper
Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data

(8)
Dynamic optimization of generalized SQL queries with horizontal 
aggregations - 2012
Carlos Ordonez, Javier García-García, Zhibo Chen
Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data

(9)
"Cut me some slack": latency-aware live migration for databases - 2012
Sean Barker, Yun Chi, Hyun Jin Moon, Hakan Hacigümüş, Prashant Shenoy
Proceedings of the 15th International Conference on Extending Database Technology

(10)
Attribute implications in similarity-based databases: semantic entailment and nonredundant bases - 2012
Radim Belohlavek, Vilem Vychodil
Proceedings of the 27th Annual ACM Symposium on Applied Computing

Erwin comments:

The ACM classification is not a "partitioning" of papers.  Each paper can be "related" to one or more subject matters in the taxonomy.  And there are two degrees of "being related" : "positively" and "somewhat".

Codd's paper is "positively" related to "Database Administration", and also "somewhat" related to "Relational Data Model".

Paper number (5) of the foregoing list is "positively" related to
"Relational Data Model".  Here's its abstract :

The SAP HANA database is the core of SAP's new data management platform. The overall goal of the SAP HANA database is to provide a generic but powerful system for different query scenarios, both transactional and analytical, on the same data representation within a highly scalable execution environment. Within this paper, we highlight the main features that differentiate the SAP HANA database from classical relational database engines. Therefore, we outline the general architecture and design criteria of the SAP HANA in a first step. In a second step, we challenge the common belief that column store data structures are only superior in analytical workloads and not well suited for transactional workloads. We outline the concept of record life cycle management to use different storage formats for the different stages of a record. We not only discuss the general concept but also dive into some of the details of how to efficiently propagate records through their life cycle and moving database entries from write-optimized to read-optimized storage formats. In summary, the paper aims at illustrating how the SAP HANA database is able to efficiently work in analytical as well as transactional workload environments."

(crying,crying,crying)

Erwin initially suggested that this is more of a To Cry or Laugh? post. But after all this, what's here to laugh about?