<?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: My personal SQL coding standards</title>
	<atom:link href="http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/</link>
	<description>Stay curious!</description>
	<lastBuildDate>Fri, 30 Jul 2010 06:32:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ron</title>
		<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-18439</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 25 Jun 2010 12:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=114#comment-18439</guid>
		<description>Commas in front of the statement might be ugly but NOT hard to maintain. That you can easyly comment out any column with comma in front is the only reason they are there.</description>
		<content:encoded><![CDATA[<p>Commas in front of the statement might be ugly but NOT hard to maintain. That you can easyly comment out any column with comma in front is the only reason they are there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meir</title>
		<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-17085</link>
		<dc:creator>Meir</dc:creator>
		<pubDate>Thu, 08 Oct 2009 21:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=114#comment-17085</guid>
		<description>Thanks everyone for your encouragement!
I wonder if any of you are using the MySQL Workbench?
(I read its documentation but setting it up and importing the DB schema intimidated me so I passed. The GUI Query Browser worked so far fine for me, thank you! Do you think however that should I try it?)
Anyway, does the WB query editor highlight it so? If not, anyone who is a WB user, please post a request for this type of highlight. I personally don&#039;t think I should if I am not at least a newbie user.
Thanks!
Meir</description>
		<content:encoded><![CDATA[<p>Thanks everyone for your encouragement!<br />
I wonder if any of you are using the MySQL Workbench?<br />
(I read its documentation but setting it up and importing the DB schema intimidated me so I passed. The GUI Query Browser worked so far fine for me, thank you! Do you think however that should I try it?)<br />
Anyway, does the WB query editor highlight it so? If not, anyone who is a WB user, please post a request for this type of highlight. I personally don&#8217;t think I should if I am not at least a newbie user.<br />
Thanks!<br />
Meir</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus</title>
		<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-17081</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Thu, 08 Oct 2009 18:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=114#comment-17081</guid>
		<description>Hi Meir,

that&#039;s indeed an excellent idea, in my career I&#039;ve also had to face &quot;some&quot; statements that where a few hundred lines and had a lot of subqueries in every flavour...

If any SQL editor developer reads this: do it!

And if you&#039;re alread implementing this, what about nested function calls? There were numerous times in my life when I spend endless minutes analyzing the structure of some DECODE ... SUBSTRING ... INSTRING ... LENGTH ... -1 ... SUBSTRING SUBSTRING SUBSTRING constructs that were just driving me crazy.

Code folding would also be nice there...

;-)</description>
		<content:encoded><![CDATA[<p>Hi Meir,</p>
<p>that&#8217;s indeed an excellent idea, in my career I&#8217;ve also had to face &#8220;some&#8221; statements that where a few hundred lines and had a lot of subqueries in every flavour&#8230;</p>
<p>If any SQL editor developer reads this: do it!</p>
<p>And if you&#8217;re alread implementing this, what about nested function calls? There were numerous times in my life when I spend endless minutes analyzing the structure of some DECODE &#8230; SUBSTRING &#8230; INSTRING &#8230; LENGTH &#8230; -1 &#8230; SUBSTRING SUBSTRING SUBSTRING constructs that were just driving me crazy.</p>
<p>Code folding would also be nice there&#8230;</p>
<p>;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-17080</link>
		<dc:creator>Xaprb</dc:creator>
		<pubDate>Thu, 08 Oct 2009 12:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=114#comment-17080</guid>
		<description>Meir, that&#039;s a great idea.  I would appreciate that too.</description>
		<content:encoded><![CDATA[<p>Meir, that&#8217;s a great idea.  I would appreciate that too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meir</title>
		<link>http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-17079</link>
		<dc:creator>Meir</dc:creator>
		<pubDate>Thu, 08 Oct 2009 11:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=114#comment-17079</guid>
		<description>One highlighting approach I never sow in SQL editors is to mark the extent and scope of a sub-query.
It would be nice to immediatly visualize where a query starts and where it ends and what is it alias.
With a convoluted and long querry, replate with joins and three or more levels of sub-queries, it is not that easy to visualize...</description>
		<content:encoded><![CDATA[<p>One highlighting approach I never sow in SQL editors is to mark the extent and scope of a sub-query.<br />
It would be nice to immediatly visualize where a query starts and where it ends and what is it alias.<br />
With a convoluted and long querry, replate with joins and three or more levels of sub-queries, it is not that easy to visualize&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
