Comments on: My personal SQL coding standards http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/ Stay curious! Fri, 29 Aug 2008 19:38:55 +0000 http://wordpress.org/?v=2.2.2 By: Anthony Altemara http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-14370 Anthony Altemara Sun, 30 Mar 2008 19:53:04 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-14370 Thanks for the ideas! Thanks for the ideas!

]]> By: GuidoMArcel http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-13349 GuidoMArcel Thu, 30 Aug 2007 09:02:46 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-13349 Hi, I tried to implement your ideas in this free online (and desktop) SQL Formatter / Beautifier: http://www.sqlinform.com Hope this is is of interest GuidoMArcel Hi,
I tried to implement your ideas in this free online (and desktop) SQL Formatter / Beautifier: http://www.sqlinform.com
Hope this is is of interest
GuidoMArcel

]]> By: Airoso http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-3036 Airoso Tue, 09 Jan 2007 02:06:59 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-3036 <p>Hi to all of you guys!<br/> I definitely agree on some of your ideas..<br/> btw, this are my ideas on some of your topics.. </p> <pre>select col1 ,col2 ,col3 … </pre> <p>i can say that this coding isn’t hard to maintain and and read.<br/> the columns can be easily spotted and the great thing about<br/> this is if you need to delete a column(specially the last of the select list), <br/> you don’t need to look for the comma b4 that column. </p> <pre>“… from table1 inner join table2 on table1.a = table2.a inner join table3 on table3.b = table1.b …” </pre> <p>and for this one, if i am correct, this coding is aimed for performance.. <br/> if the left table has the foreign key and the right table has the primary<br/> key, the matching will be more faster than the way around because the <br/>value that will be used for equality is a primary key. well, that was <br/>all i had in my mind. if i am wrong or whatsoever, i’ll be happy to be <br/>corrected. anyway, great thanks to you, Xaprb, for providing this <br/>great topic! :) </p> Hi to all of you guys!

I definitely agree on some of your ideas..

btw, this are my ideas on some of your topics.. 

select
     col1
     ,col2
     ,col3 …

i can say that this coding isn’t hard to maintain and and read.

the columns can be easily spotted and the great thing about

this is if you need to delete a column(specially the last of the select list),

you don’t need to look for the comma b4 that column. 

“… from table1 inner join table2 on table1.a = table2.a
inner join table3 on table3.b = table1.b …”

and for this one, if i am correct, this coding is aimed for performance..

if the left table has the foreign key and the right table has the primary

key, the matching will be more faster than the way around because the
value that will be used for equality is a primary key. well, that was
all i had in my mind. if i am wrong or whatsoever, i’ll be happy to be
corrected. anyway, great thanks to you, Xaprb, for providing this
great topic! :)

]]> By: Chris Lacey http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-1770 Chris Lacey Tue, 12 Sep 2006 09:38:44 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-1770 <p>Very much like, and agree with, your thinking on this (other than the fact that I usually capitalise keywords since, in my world, chunks of SQL can often get embedded in a string whereby the editor won't colour them).</p> <p>It's odd that a SQL coding standard seems to be such an unknown concept, whereas in fact the looseness of the language (case insensitivity etc) demands it all the more.</p> <p>I put together my own thoughts on this a while ago (at <a href="http://www.cslacey.co.uk/TSQLCodingStandards.pdf">http://www.cslacey.co.uk/TSQLCodingStandards.pdf</a> ). Probably don't cover as much ground as you, but of those things I do mention, I agree with you almost entirely.</p> Very much like, and agree with, your thinking on this (other than the fact that I usually capitalise keywords since, in my world, chunks of SQL can often get embedded in a string whereby the editor won’t colour them).

It’s odd that a SQL coding standard seems to be such an unknown concept, whereas in fact the looseness of the language (case insensitivity etc) demands it all the more.

I put together my own thoughts on this a while ago (at http://www.cslacey.co.uk/TSQLCodingStandards.pdf ). Probably don’t cover as much ground as you, but of those things I do mention, I agree with you almost entirely.

]]> By: Xaprb http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-1406 Xaprb Wed, 09 Aug 2006 13:53:24 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-1406 <p><a href="http://x7net.com/~access/index.php">Yu Tang</a> has <a href="http://x7net.com/~access/index.php?option=com_content&task=view&id=2&Itemid=9&limit=1&limitstart=1">translated this article into Japanese</a> and published it on his website.</p> Yu Tang has translated this article into Japanese and published it on his website.

]]> By: Archimedes Trajano http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-435 Archimedes Trajano Wed, 17 May 2006 15:46:32 +0000 http://www.xaprb.com/blog/2006/04/26/sql-coding-standards/#comment-435 <p>I agree with your style. Except I tend to use UPPER_CASE for my object names since that would jive with what the DBA sees. I still use lowercase for my keywords like "select" though.</p> <p>I try to avoid this sort of hassle by using Hibernate nowadays though.</p> I agree with your style. Except I tend to use UPPER_CASE for my object names since that would jive with what the DBA sees. I still use lowercase for my keywords like “select” though.

I try to avoid this sort of hassle by using Hibernate nowadays though.

]]>