On 3/13/15 11:39 AM, Michael Brunnbauer wrote:
Hello Kingsley,yes, ACID and traditional RDBMS are for loosers. Think Big instead! Big data Big exploitation Big complexity Big technical debt Interest is payable to OpenLink Software. Regards, Michael Brunnbauer
Michael,I hope you are not assuming that I meant: ACID and tradition RDBMS are for losers?
My fundamental point is simply about the fact that RDBMS doesn't mean SQL RDBMS. Thus, ACID has nothing to do with being Relational, in regards to Database document construction and/or management. It has everything to do with the Atomicity, Concurrency, Isolation, and Durability of operations on databases performed by RDBMS applications.
A traditional RDBMS != SQL RDBMS either. That has never ever been the case. Kingsley
On Fri, Mar 13, 2015 at 10:05:54AM -0400, Kingsley Idehen wrote:On 3/12/15 5:38 PM, Paul Houle wrote:The goal is to show that you can do the same things you do with a relational database, and maybe *just* a little bit more.Every RDF store is a relational database management system (RDBMS). As you know, an RDF compliant RDBMS simply group sets of RDF 3-tuples by statement predicate. We can't continue to concede the notion of a relational database management to SQL relational database management systems (sets of n-tuples grouped by Table Name). Maybe we should start referring to SPARQL compliant RDF stores as SPARQL Relational Database Management Systems, just like SQL Relational Database Management Systems which have now become synonymous with Relational Database Management System. Then "just a little more" becomes much closer to demonstrable reconciliation of "the truth, the whole truth, and nothing but the truth, in regards to relations, databases, and database management systems" :) ACID has nothing to do with what constitutes an RDBMS either, that's an a useful, but optional feature of any RDBMS. So don't fall for that baloney laden push-back when taking the SPARQL RDBMS position. We MUST end the SQL RDBMS power-grab! It has done a major disservice to the entire DBMS industry, over the last 40+ years. You have a multi-billion dollar industry that's fundamentally about companies and individuals that are data-access-heavy and data-exploitation-challenged i.e., they have tons of data ("Big Data" these days), but still can't achieve basic agility goals in regards to: accessing, integrating, and moving data effectively to the right people, at the right time, in the right form, and in appropriate context etc.. Links: [1] http://bit.ly/spasql-sql-querying-based-on-sparql-table-relation -- demonstrating that relations are relations (even when the underlying tuple organizations vary e.g., when organized as sql relational tables or rdf statements graphs) . [2] http://www.openlinksw.com/c/9C5DNHYW -- Relation . [3] http://www.openlinksw.com/c/9BVTLIAG -- SQL Relation . [4] http://www.openlinksw.com/c/9BH3NH7S -- RDF Relation. [5] http://www.openlinksw.com/c/9BDLVDX3 -- Differentiating "Database" (a Document comprised of sets of Relations [Data] ) from "Database Management System" (software for indexing and querying culled from Database Documents). -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
smime.p7s
Description: S/MIME Cryptographic Signature
