<?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 for code.openark.org</title>
	<atom:link href="http://code.openark.org/blog/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://code.openark.org/blog</link>
	<description>Blog by Shlomi Noach</description>
	<lastBuildDate>Thu, 11 Mar 2010 12:08:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Proper SQL table alias use conventions by shlomi</title>
		<link>http://code.openark.org/blog/mysql/proper-sql-table-alias-use-conventions/comment-page-1#comment-11378</link>
		<dc:creator>shlomi</dc:creator>
		<pubDate>Thu, 11 Mar 2010 12:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2156#comment-11378</guid>
		<description>Hmmm... something still missing in the query...</description>
		<content:encoded><![CDATA[<p>Hmmm&#8230; something still missing in the query&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Proper SQL table alias use conventions by shlomi</title>
		<link>http://code.openark.org/blog/mysql/proper-sql-table-alias-use-conventions/comment-page-1#comment-11376</link>
		<dc:creator>shlomi</dc:creator>
		<pubDate>Thu, 11 Mar 2010 11:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2156#comment-11376</guid>
		<description>@Bill

Thank you. Yes, I completely agree. Having a convention is the most important part; I only gave my recommendations.
Indeed I did not tackle the self join issue. Thank you for your example! (I hope I fixed your code correctly?)</description>
		<content:encoded><![CDATA[<p>@Bill</p>
<p>Thank you. Yes, I completely agree. Having a convention is the most important part; I only gave my recommendations.<br />
Indeed I did not tackle the self join issue. Thank you for your example! (I hope I fixed your code correctly?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Proper SQL table alias use conventions by Bill Karwin</title>
		<link>http://code.openark.org/blog/mysql/proper-sql-table-alias-use-conventions/comment-page-1#comment-11372</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Thu, 11 Mar 2010 09:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2156#comment-11372</guid>
		<description>Er, part of my example query above was eaten. :(</description>
		<content:encoded><![CDATA[<p>Er, part of my example query above was eaten. <img src='http://code.openark.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Proper SQL table alias use conventions by Bill Karwin</title>
		<link>http://code.openark.org/blog/mysql/proper-sql-table-alias-use-conventions/comment-page-1#comment-11371</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Thu, 11 Mar 2010 09:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2156#comment-11371</guid>
		<description>As with any other coding language, the specific details of your coding conventions are not as important as *having* coding conventions, and following them more or less consistently.

I think your recommendations are fine.  You are, however, missing any recommendations for how to name aliases when you use self-joins.

I find that sometimes, the alias may even be longer than the table name:
&lt;pre&gt;
SELECT later_customer.*
FROM 
  customers AS first_customer
  JOIN customers AS later_customer ON (first_customer.cust_id = hypothetical_earlier_customer.cust_id)
WHERE 
  hypothetical_earlier_customer.cust_id IS NULL;
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>As with any other coding language, the specific details of your coding conventions are not as important as *having* coding conventions, and following them more or less consistently.</p>
<p>I think your recommendations are fine.  You are, however, missing any recommendations for how to name aliases when you use self-joins.</p>
<p>I find that sometimes, the alias may even be longer than the table name:</p>
<pre>
SELECT later_customer.*
FROM
  customers AS first_customer
  JOIN customers AS later_customer ON (first_customer.cust_id = hypothetical_earlier_customer.cust_id)
WHERE
  hypothetical_earlier_customer.cust_id IS NULL;
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mk-schema-change? Check out ideas from oak-online-alter-table by shlomi</title>
		<link>http://code.openark.org/blog/mysql/mk-schema-change-check-out-ideas-from-oak-online-alter-table/comment-page-1#comment-11340</link>
		<dc:creator>shlomi</dc:creator>
		<pubDate>Wed, 10 Mar 2010 19:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2144#comment-11340</guid>
		<description>I think your quote on triggers took some 30% of our entire conversation :D

By all means, this is not a discussion on triggers. There&#039;s an algorithm beside the triggers here.</description>
		<content:encoded><![CDATA[<p>I think your quote on triggers took some 30% of our entire conversation <img src='http://code.openark.org/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>By all means, this is not a discussion on triggers. There&#8217;s an algorithm beside the triggers here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on mk-schema-change? Check out ideas from oak-online-alter-table by Mark Callaghan</title>
		<link>http://code.openark.org/blog/mysql/mk-schema-change-check-out-ideas-from-oak-online-alter-table/comment-page-1#comment-11338</link>
		<dc:creator>Mark Callaghan</dc:creator>
		<pubDate>Wed, 10 Mar 2010 19:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=2144#comment-11338</guid>
		<description>Thanks for being specific with my quote on triggers. I am not willing to use them in production. Maybe I am not able to use them. They might work great for others but I have enough features to worry about and am cautious to take on more. If Shlomi or another MySQL expert suggests you should use triggers for a specific problem, then by all means do so.</description>
		<content:encoded><![CDATA[<p>Thanks for being specific with my quote on triggers. I am not willing to use them in production. Maybe I am not able to use them. They might work great for others but I have enough features to worry about and am cautious to take on more. If Shlomi or another MySQL expert suggests you should use triggers for a specific problem, then by all means do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tip: faster than TRUNCATE by shlomi</title>
		<link>http://code.openark.org/blog/mysql/tip-faster-than-truncate/comment-page-1#comment-11334</link>
		<dc:creator>shlomi</dc:creator>
		<pubDate>Wed, 10 Mar 2010 16:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=1896#comment-11334</guid>
		<description>@Hans,
Well, I would do well with 8-10 seconds. However, as I described, I waited for long minutes. Connections got into Locked state. Nothing would happen (on one occasion I waited for 15 minutes before calling it off).</description>
		<content:encoded><![CDATA[<p>@Hans,<br />
Well, I would do well with 8-10 seconds. However, as I described, I waited for long minutes. Connections got into Locked state. Nothing would happen (on one occasion I waited for 15 minutes before calling it off).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tip: faster than TRUNCATE by Hans-Henrik</title>
		<link>http://code.openark.org/blog/mysql/tip-faster-than-truncate/comment-page-1#comment-11332</link>
		<dc:creator>Hans-Henrik</dc:creator>
		<pubDate>Wed, 10 Mar 2010 13:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=1896#comment-11332</guid>
		<description>The big difference, i think is the time the table &#039;log_table&#039; is unavailable.

If you truncate, the table will be locked until the space has been freed (8-10 seconds for _very_ large tables, if you have IO at the same time). If you do the renaming first, the empty table will appear _very_ fast, while the dropping of the old table does not involve locking of any table that is in use, and so - probably doesn&#039;t matter much if it takes a few seconds.</description>
		<content:encoded><![CDATA[<p>The big difference, i think is the time the table &#8216;log_table&#8217; is unavailable.</p>
<p>If you truncate, the table will be locked until the space has been freed (8-10 seconds for _very_ large tables, if you have IO at the same time). If you do the renaming first, the empty table will appear _very_ fast, while the dropping of the old table does not involve locking of any table that is in use, and so &#8211; probably doesn&#8217;t matter much if it takes a few seconds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tip: faster than TRUNCATE by shlomi</title>
		<link>http://code.openark.org/blog/mysql/tip-faster-than-truncate/comment-page-1#comment-11328</link>
		<dc:creator>shlomi</dc:creator>
		<pubDate>Wed, 10 Mar 2010 11:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=1896#comment-11328</guid>
		<description>@Vojtech,
Thank you!</description>
		<content:encoded><![CDATA[<p>@Vojtech,<br />
Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tip: faster than TRUNCATE by Vojtech Kurka</title>
		<link>http://code.openark.org/blog/mysql/tip-faster-than-truncate/comment-page-1#comment-11327</link>
		<dc:creator>Vojtech Kurka</dc:creator>
		<pubDate>Wed, 10 Mar 2010 11:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://code.openark.org/blog/?p=1896#comment-11327</guid>
		<description>Morgan, large ibd files are not the only cause. Shlomi, It&#039;s a bug, just look at:  http://bugs.mysql.com/bug.php?id=35077 http://bugs.mysql.com/bug.php?id=51325 http://bugs.mysql.com/bug.php?id=51557</description>
		<content:encoded><![CDATA[<p>Morgan, large ibd files are not the only cause. Shlomi, It&#8217;s a bug, just look at:  <a href="http://bugs.mysql.com/bug.php?id=35077" rel="nofollow">http://bugs.mysql.com/bug.php?id=35077</a> <a href="http://bugs.mysql.com/bug.php?id=51325" rel="nofollow">http://bugs.mysql.com/bug.php?id=51325</a> <a href="http://bugs.mysql.com/bug.php?id=51557" rel="nofollow">http://bugs.mysql.com/bug.php?id=51557</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
