<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What is a relational database?</title>
	<atom:link href="http://explainextended.com/2009/08/23/what-is-a-relational-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://explainextended.com/2009/08/23/what-is-a-relational-database/</link>
	<description>How to create fast database queries</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:19:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Quassnoi</title>
		<link>http://explainextended.com/2009/08/23/what-is-a-relational-database/comment-page-1/#comment-78</link>
		<dc:creator>Quassnoi</dc:creator>
		<pubDate>Mon, 21 Sep 2009 20:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://explainextended.com/?p=2759#comment-78</guid>
		<description>Using this analogy, hierarchical and network models can better be thought of as hardware implementations of a model, while SQL is the software implementation (assembly).

Hardware things are faster when implemented properly but they are extremely hard to design, even more hard to redesign and slow if designed improperly.</description>
		<content:encoded><![CDATA[<p>Using this analogy, hierarchical and network models can better be thought of as hardware implementations of a model, while SQL is the software implementation (assembly).</p>
<p>Hardware things are faster when implemented properly but they are extremely hard to design, even more hard to redesign and slow if designed improperly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandr Savinov</title>
		<link>http://explainextended.com/2009/08/23/what-is-a-relational-database/comment-page-1/#comment-77</link>
		<dc:creator>Alexandr Savinov</dc:creator>
		<pubDate>Mon, 21 Sep 2009 20:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://explainextended.com/?p=2759#comment-77</guid>
		<description>SQL can be thought of as assemply language of the database world. It does not impose almost any restrictions on operations performed with data and therefore an arbitrary data model can be implemented using it just as any high level programming language can be implemented using assembler. In particular, both hierarchical and network models as well as many other models could be implemented using SQL. Moreover, it is precisely what normally happens - database developers think of data in one way but have to implement their design in the only available langauge (SQL). What do you think about this role of SQL (and relational model)?</description>
		<content:encoded><![CDATA[<p>SQL can be thought of as assemply language of the database world. It does not impose almost any restrictions on operations performed with data and therefore an arbitrary data model can be implemented using it just as any high level programming language can be implemented using assembler. In particular, both hierarchical and network models as well as many other models could be implemented using SQL. Moreover, it is precisely what normally happens &#8211; database developers think of data in one way but have to implement their design in the only available langauge (SQL). What do you think about this role of SQL (and relational model)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

