<?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: PowerDNS MySQL INT limit reached.</title>
	<atom:link href="http://www.schwer.us/journal/2008/03/06/powerdns-mysql-int-limit-reached/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schwer.us/journal/2008/03/06/powerdns-mysql-int-limit-reached/</link>
	<description>Logging the activities of four Schwers.</description>
	<lastBuildDate>Sun, 01 May 2011 20:06:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: dms</title>
		<link>http://www.schwer.us/journal/2008/03/06/powerdns-mysql-int-limit-reached/comment-page-1/#comment-44231</link>
		<dc:creator>dms</dc:creator>
		<pubDate>Thu, 03 Apr 2008 01:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.schwer.us/journal/2008/03/06/powerdns-mysql-int-limit-reached/#comment-44231</guid>
		<description>Your fix works, Augie, but it&#039;s a) slow and b) requires unnecessary storage space.

Much better:
ALTER TABLE records MODIFY id INT UNSIGNED AUTO_INCREMENT NOT NULL;

The real key there is the &quot;unsigned&quot; - it gives you twice as much storage in the same amount of space. And the query runs nearly simultaneously, as opposed to the hour+ it takes to change the size of a field in a table that long.

Another observation: why are all of the fields in the records table nullable? Best practice is usually to make them non-nullable unless for some reason nulls are really needed (and they&#039;re usually no).

JFWIW.</description>
		<content:encoded><![CDATA[<p>Your fix works, Augie, but it&#8217;s a) slow and b) requires unnecessary storage space.</p>
<p>Much better:<br />
ALTER TABLE records MODIFY id INT UNSIGNED AUTO_INCREMENT NOT NULL;</p>
<p>The real key there is the &#8220;unsigned&#8221; &#8211; it gives you twice as much storage in the same amount of space. And the query runs nearly simultaneously, as opposed to the hour+ it takes to change the size of a field in a table that long.</p>
<p>Another observation: why are all of the fields in the records table nullable? Best practice is usually to make them non-nullable unless for some reason nulls are really needed (and they&#8217;re usually no).</p>
<p>JFWIW.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

