<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Database management system choices – beyond relational</title>
	<atom:link href="http://www.dbms2.com/2008/02/15/non-relational-database-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2008/02/15/non-relational-database-management/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Sun, 20 Jul 2008 01:33:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Daniel Weinreb</title>
		<link>http://www.dbms2.com/2008/02/15/non-relational-database-management/#comment-72930</link>
		<dc:creator>Daniel Weinreb</dc:creator>
		<pubDate>Sat, 16 Feb 2008 14:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/non-relational-database-management/#comment-72930</guid>
		<description>I completely agree.

One way you can do this with an RDBMS is to let the relational schema merely be a meta-schema.  For example, represent RDF as triples, and have one relational table with three columns, and put everything in there.

There are, of course, disadvantages to this approach.  It means that what you think of as the schema is not actually represented by the RDBMS.  That means you can't easily take advantage of the RDBMS's integrity features, and it's harder to control physical layout, just to mention two.

You can actually modify the schema of an RDBMS dynamically with DDL statements, but it's not the "sweet spot".  I have to admit that doing this in ObjectStore (the object-oriented DBMS that I co-designed), which we called "schema evolution", was also not a piece of cake; it wasn't designed for that.  However, the XML database that we built on top of ObjectStore did provide that kind of flexibility.</description>
		<content:encoded><![CDATA[<p>I completely agree.</p>
<p>One way you can do this with an RDBMS is to let the relational schema merely be a meta-schema.  For example, represent RDF as triples, and have one relational table with three columns, and put everything in there.</p>
<p>There are, of course, disadvantages to this approach.  It means that what you think of as the schema is not actually represented by the RDBMS.  That means you can&#8217;t easily take advantage of the RDBMS&#8217;s integrity features, and it&#8217;s harder to control physical layout, just to mention two.</p>
<p>You can actually modify the schema of an RDBMS dynamically with DDL statements, but it&#8217;s not the &#8220;sweet spot&#8221;.  I have to admit that doing this in ObjectStore (the object-oriented DBMS that I co-designed), which we called &#8220;schema evolution&#8221;, was also not a piece of cake; it wasn&#8217;t designed for that.  However, the XML database that we built on top of ObjectStore did provide that kind of flexibility.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
