<?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: Why SQL Sucks</title>
	<atom:link href="http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/</link>
	<description>Softwaredevelopment, Projectmanagement, Qualitymanagement and all things &#34;schauderhaft&#34;</description>
	<lastBuildDate>Tue, 07 Feb 2012 23:24:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jamin Ohmoto-Frederick</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-4440</link>
		<dc:creator>Jamin Ohmoto-Frederick</dc:creator>
		<pubDate>Tue, 08 Nov 2011 05:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-4440</guid>
		<description>I have been trying to figure this out too, as SQL has always seemed clunky and unintuitive to me.  I happened across The Third Manifesto by Date &amp; Darwen a few years ago, where there is a clear criticism of the current, sad state of affairs. Something that was once a simple model (original Codd model based on relational algebra) went astray and grew into the ugly beast of SQL.  Not only that but the three-value logic that includes UNKNOWN (i.e., NULL) can lead to data inconsistencies.</description>
		<content:encoded><![CDATA[<p>I have been trying to figure this out too, as SQL has always seemed clunky and unintuitive to me.  I happened across The Third Manifesto by Date &amp; Darwen a few years ago, where there is a clear criticism of the current, sad state of affairs. Something that was once a simple model (original Codd model based on relational algebra) went astray and grew into the ugly beast of SQL.  Not only that but the three-value logic that includes UNKNOWN (i.e., NULL) can lead to data inconsistencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-4111</link>
		<dc:creator>andy</dc:creator>
		<pubDate>Mon, 22 Aug 2011 20:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-4111</guid>
		<description>I find it curious how many commenters are actually defending SQL.

SQL DOES suck.  Its syntax is clunky, and outdated.  Not only that, but the syntax hasn&#039;t even evolved since it was originally created.  Not one bit.  Sure, more functionality has been added over time, but that&#039;s about it.

I&#039;d have to single out the JOIN syntax as a key example of what I&#039;m talking about.

With Hibernate, I can simply say something like this (don&#039;t get me wrong, I hate Hibernate as well):

select id 
from table1 
where
table1.table2.table3.table4.table5.table6.something = &quot;blah&quot;

Quite a long and involved query, to be sure, but the above syntax makes it about as succinct as it can get.

Case in point -&gt; Now consider the monstrosity you&#039;d get with the same query, in SQL:

select t1.id
from table1 as t1
inner join table2 as t2
on t1.foo = t2.bar
inner join table3 as t3
on t2.foo = t3.bar
inner join table4 as t4
on t3.foo = t4.bar
inner join table5 as t5
on t4.foo = t5.bar
inner join table6 as t6
on t5.foo = t6.bar
where t6..something = &quot;blah&quot;

Again, SQL&#039;s syntax is one of the most obtuse I&#039;ve ever encountered, and it would do well to evolve even slightly</description>
		<content:encoded><![CDATA[<p>I find it curious how many commenters are actually defending SQL.</p>
<p>SQL DOES suck.  Its syntax is clunky, and outdated.  Not only that, but the syntax hasn&#8217;t even evolved since it was originally created.  Not one bit.  Sure, more functionality has been added over time, but that&#8217;s about it.</p>
<p>I&#8217;d have to single out the JOIN syntax as a key example of what I&#8217;m talking about.</p>
<p>With Hibernate, I can simply say something like this (don&#8217;t get me wrong, I hate Hibernate as well):</p>
<p>select id<br />
from table1<br />
where<br />
table1.table2.table3.table4.table5.table6.something = &#8220;blah&#8221;</p>
<p>Quite a long and involved query, to be sure, but the above syntax makes it about as succinct as it can get.</p>
<p>Case in point -&gt; Now consider the monstrosity you&#8217;d get with the same query, in SQL:</p>
<p>select t1.id<br />
from table1 as t1<br />
inner join table2 as t2<br />
on t1.foo = t2.bar<br />
inner join table3 as t3<br />
on t2.foo = t3.bar<br />
inner join table4 as t4<br />
on t3.foo = t4.bar<br />
inner join table5 as t5<br />
on t4.foo = t5.bar<br />
inner join table6 as t6<br />
on t5.foo = t6.bar<br />
where t6..something = &#8220;blah&#8221;</p>
<p>Again, SQL&#8217;s syntax is one of the most obtuse I&#8217;ve ever encountered, and it would do well to evolve even slightly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-3625</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 31 May 2011 01:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-3625</guid>
		<description>I&#039;m glad everyone is writing about this.  I&#039;m currently starting a PL/SQL class.
Frankly, it&#039;s frustrating and time-consuming to learn.  The entity relationship model is easy to understand in an abstract manner.  The language used to articulate the model and manipulate its information is difficult.
I have not gotten as frustrated when learning .Net, Java, data structures, etc.  It&#039;s not that I can&#039;t easily imagine solutions to problems using sql.  But I can&#039;t easily implement or challenge my understanding of concepts like I can in other languages.  I can&#039;t just jump right into testing my understanding of aggregate function with my own made up problem as easily as I could test my knowledge of a queue, gui placement, serial over bluetooth, interfaces, etc.  
Constructively, do I know another(or better) way? No, I don&#039;t have enough experience to know of any other way but I do have enough experience to say it is frustrating.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad everyone is writing about this.  I&#8217;m currently starting a PL/SQL class.<br />
Frankly, it&#8217;s frustrating and time-consuming to learn.  The entity relationship model is easy to understand in an abstract manner.  The language used to articulate the model and manipulate its information is difficult.<br />
I have not gotten as frustrated when learning .Net, Java, data structures, etc.  It&#8217;s not that I can&#8217;t easily imagine solutions to problems using sql.  But I can&#8217;t easily implement or challenge my understanding of concepts like I can in other languages.  I can&#8217;t just jump right into testing my understanding of aggregate function with my own made up problem as easily as I could test my knowledge of a queue, gui placement, serial over bluetooth, interfaces, etc.<br />
Constructively, do I know another(or better) way? No, I don&#8217;t have enough experience to know of any other way but I do have enough experience to say it is frustrating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Coleman</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-3395</link>
		<dc:creator>Peter Coleman</dc:creator>
		<pubDate>Sun, 17 Apr 2011 11:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-3395</guid>
		<description>Well, SQL may suck that is true. A lot of things in the IT business suck.  At least SQL also swallows what it sucks.</description>
		<content:encoded><![CDATA[<p>Well, SQL may suck that is true. A lot of things in the IT business suck.  At least SQL also swallows what it sucks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patatpatat</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-1196</link>
		<dc:creator>Patatpatat</dc:creator>
		<pubDate>Sat, 27 Nov 2010 06:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-1196</guid>
		<description>SQL easy to understand? Perhaps. But it&#039;s a chore to perform any moderately complex calculation just with SQL alone. Yes, any SQL sympathetic would say that calculations is not what SQL is for. But it would make development so much easier if something like the model clause was implemented more widely.</description>
		<content:encoded><![CDATA[<p>SQL easy to understand? Perhaps. But it&#8217;s a chore to perform any moderately complex calculation just with SQL alone. Yes, any SQL sympathetic would say that calculations is not what SQL is for. But it would make development so much easier if something like the model clause was implemented more widely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-1096</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sat, 30 Oct 2010 17:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-1096</guid>
		<description>Like Lee above, I have programmed in many languages, and I agree -- SQL sucks.  It appears to have been designed by people who only wanted to ensure their job security, like bureaucrats who create needlessly arcane processes.

To Dave above: simpler is a relative term.  Because something is simple to you does not mean it could not be simpler than it is.</description>
		<content:encoded><![CDATA[<p>Like Lee above, I have programmed in many languages, and I agree &#8212; SQL sucks.  It appears to have been designed by people who only wanted to ensure their job security, like bureaucrats who create needlessly arcane processes.</p>
<p>To Dave above: simpler is a relative term.  Because something is simple to you does not mean it could not be simpler than it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave_Eels</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-714</link>
		<dc:creator>Dave_Eels</dc:creator>
		<pubDate>Thu, 02 Sep 2010 08:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-714</guid>
		<description>If you cant understand that beauty. Try going back to SQL 101. 

The Solution is actually very simple. If you dont like SQL dont use it. If you dont want to use SQL / dont dislike it.  You will very soon find out how easy it really is comparing to other Database Sotware. Try adding the same effort into learning SQL as Complaining about it. It sometimes helps. 

Tutorial 1
 - Making the First Letter of a Word Uppercase. 
- Hold in shift and press the letter. ( Dont make it difficult by turning Caps Lock on  , Press the letter and turn caps lock off )

Everything is Simpler if you know how to use it.</description>
		<content:encoded><![CDATA[<p>If you cant understand that beauty. Try going back to SQL 101. </p>
<p>The Solution is actually very simple. If you dont like SQL dont use it. If you dont want to use SQL / dont dislike it.  You will very soon find out how easy it really is comparing to other Database Sotware. Try adding the same effort into learning SQL as Complaining about it. It sometimes helps. </p>
<p>Tutorial 1<br />
 &#8211; Making the First Letter of a Word Uppercase.<br />
- Hold in shift and press the letter. ( Dont make it difficult by turning Caps Lock on  , Press the letter and turn caps lock off )</p>
<p>Everything is Simpler if you know how to use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-656</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 30 Jul 2010 21:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-656</guid>
		<description>I completley agree: SQL sucks. 
I do C,C++,Python,Pascal, embedded everything etc and SQL just sucks as a language. It reminds me of the first BASIC. I often just find myself dumping it all to CSV and parsing it a homebrew info-structure way.</description>
		<content:encoded><![CDATA[<p>I completley agree: SQL sucks.<br />
I do C,C++,Python,Pascal, embedded everything etc and SQL just sucks as a language. It reminds me of the first BASIC. I often just find myself dumping it all to CSV and parsing it a homebrew info-structure way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rolfen</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-595</link>
		<dc:creator>rolfen</dc:creator>
		<pubDate>Sun, 04 Jul 2010 21:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-595</guid>
		<description>So, what&#039;s the alternative?</description>
		<content:encoded><![CDATA[<p>So, what&#8217;s the alternative?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Schauder</title>
		<link>http://blog.schauderhaft.de/2010/02/15/why-sql-sucks/comment-page-1/#comment-426</link>
		<dc:creator>Jens Schauder</dc:creator>
		<pubDate>Fri, 09 Apr 2010 06:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schauderhaft.de/?p=414#comment-426</guid>
		<description>Hi notnot,
ich habe keinerlei Interesse SQL durch etwas imperatives zu ersetzen. In der Tat ist die deklarative Natur von SQL eine Stärke, ebenso wie die mathematischen Fundamente.

Das ist aber in keiner Weise ein Gegenargument gegen meine Argumente. Mein Beispiel von Fortran als moderne Sprache war in dieser Hinsicht vielleicht etwas ungeschickt. Es ging mir dabei nur um ein Beispiel für eine Sprache, die zumindest grundlegende Mechanismen der Modularisierung unterstützt.</description>
		<content:encoded><![CDATA[<p>Hi notnot,<br />
ich habe keinerlei Interesse SQL durch etwas imperatives zu ersetzen. In der Tat ist die deklarative Natur von SQL eine Stärke, ebenso wie die mathematischen Fundamente.</p>
<p>Das ist aber in keiner Weise ein Gegenargument gegen meine Argumente. Mein Beispiel von Fortran als moderne Sprache war in dieser Hinsicht vielleicht etwas ungeschickt. Es ging mir dabei nur um ein Beispiel für eine Sprache, die zumindest grundlegende Mechanismen der Modularisierung unterstützt.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

