<?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: Naming Conventions In MySQL Revised.</title>
	<atom:link href="http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/feed/" rel="self" type="application/rss+xml" />
	<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/</link>
	<description>You will probably want some waders, a pick axe, and one of those hats with a light on it before you go in here.</description>
	<pubDate>Tue, 06 Jan 2009 08:53:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Wes Maldonado</title>
		<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/#comment-1543</link>
		<dc:creator>Wes Maldonado</dc:creator>
		<pubDate>Wed, 15 Mar 2006 19:30:17 +0000</pubDate>
		<guid isPermaLink="false">/?p=37#comment-1543</guid>
		<description>Gavin, 

I'm all for standard naming conventions because you write code for people, not the compiler.  Which is why I asked about "the people" in my comments.  I was poking fun at Eric because he mentions optimization in a post that is about naming conventions.

And you are correct, I'm an idiot; ask Eric. 

Wes</description>
		<content:encoded><![CDATA[<p>Gavin, </p>
<p>I&#8217;m all for standard naming conventions because you write code for people, not the compiler.  Which is why I asked about &#8220;the people&#8221; in my comments.  I was poking fun at Eric because he mentions optimization in a post that is about naming conventions.</p>
<p>And you are correct, I&#8217;m an idiot; ask Eric. </p>
<p>Wes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin Minor</title>
		<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/#comment-226</link>
		<dc:creator>Gavin Minor</dc:creator>
		<pubDate>Thu, 14 Apr 2005 10:53:44 +0000</pubDate>
		<guid isPermaLink="false">/?p=37#comment-226</guid>
		<description>I think EricB's comments are perfectly accurate.  

Wes Maldonado, you're an idiot.  It's not "only" because it's easier for MySQL to optimize, it's because it's self documenting, logical, and much easier to do it this way.  To anybody that DOESNT name their primary key's and foreign keys this way - I say - you're an idiot.

Also, prefixing your primary and foreign keys with pk &#038; fk is just stupid.  Only an idiot would do that.

Also, all uppercase is APPALLING practise.  A true sign of an idiot.</description>
		<content:encoded><![CDATA[<p>I think EricB&#8217;s comments are perfectly accurate.  </p>
<p>Wes Maldonado, you&#8217;re an idiot.  It&#8217;s not &#8220;only&#8221; because it&#8217;s easier for MySQL to optimize, it&#8217;s because it&#8217;s self documenting, logical, and much easier to do it this way.  To anybody that DOESNT name their primary key&#8217;s and foreign keys this way - I say - you&#8217;re an idiot.</p>
<p>Also, prefixing your primary and foreign keys with pk &#038; fk is just stupid.  Only an idiot would do that.</p>
<p>Also, all uppercase is APPALLING practise.  A true sign of an idiot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: langdon</title>
		<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/#comment-222</link>
		<dc:creator>langdon</dc:creator>
		<pubDate>Mon, 04 Apr 2005 22:04:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=37#comment-222</guid>
		<description>I find your rules to be fine for clarity and comprehension, but annoying when building SQL when joining 1 or more tables.  I like to prefix my primary keys and foreign keys with pk and fk.  That way I don't have preface the field name with "TABLE." or give the tables aliases.

I also like my TABLES and COLUMNS to be in UPPERCASE (except for the pk/fk part).  It's prettier that way.  If this were a fixed width font, I would also demonstrate my lovely way of indenting my queries in code.

PS: I don't know how any of my preferences help/hurt the optimizer.</description>
		<content:encoded><![CDATA[<p>I find your rules to be fine for clarity and comprehension, but annoying when building SQL when joining 1 or more tables.  I like to prefix my primary keys and foreign keys with pk and fk.  That way I don&#8217;t have preface the field name with &#8220;TABLE.&#8221; or give the tables aliases.</p>
<p>I also like my TABLES and COLUMNS to be in UPPERCASE (except for the pk/fk part).  It&#8217;s prettier that way.  If this were a fixed width font, I would also demonstrate my lovely way of indenting my queries in code.</p>
<p>PS: I don&#8217;t know how any of my preferences help/hurt the optimizer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wes Maldonado</title>
		<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/#comment-218</link>
		<dc:creator>Wes Maldonado</dc:creator>
		<pubDate>Thu, 24 Mar 2005 21:33:20 +0000</pubDate>
		<guid isPermaLink="false">/?p=37#comment-218</guid>
		<description>Actually, why would you want to name a column something because it makes it easier for the optimizer?  What about the people?  Tell me about the people.</description>
		<content:encoded><![CDATA[<p>Actually, why would you want to name a column something because it makes it easier for the optimizer?  What about the people?  Tell me about the people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wes Maldonado</title>
		<link>http://ebergen.net/wordpress/2005/03/24/the-mysql-rules-rewritten/#comment-217</link>
		<dc:creator>Wes Maldonado</dc:creator>
		<pubDate>Thu, 24 Mar 2005 21:32:40 +0000</pubDate>
		<guid isPermaLink="false">/?p=37#comment-217</guid>
		<description>Why would you want to name a table something just because it is easier for the optimizer?</description>
		<content:encoded><![CDATA[<p>Why would you want to name a table something just because it is easier for the optimizer?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
