[no subject]

No. The next available use will be 2, then 3 etc. You will wind up with
duplicates.

If the auto-increment column is the primary index, you will see at the
least errors and at the worst a crash (most likely during a routine
reindex run after a series of inserts).

If you are flat out of numbers, you will need to either raise the
MAX_SEQUENCE (I don't think that's the correct variable name and I'm not
sure it's settable) or script a renumbering of the tables after a vacuum
if the largest sequence number has already been hit. From Mysql pages:


> When an AUTO_INCREMENT column runs out of values, InnoDB wraps a BIGINT
>  to -9223372036854775808 and BIGINT UNSIGNED to 1. However, BIGINT
>  values have 64 bits, so do note that if you were to insert one million
>  rows per second, it would still take nearly three hundred thousand
>  years before BIGINT reached its upper bound. With all other integer
>  type columns, a duplicate-key error results. This is similar to how
>  MyISAM works, because it is mostly general MySQL behavior and not
>  about any storage engine in particular.
> 

So the AUTO_INCREMENT process uses a 64bit Integer so running out is not
really a big issue.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO &amp; Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
<a  rel="nofollow" href="http://www.localnetsolutions.com";>http://www.localnetsolutions.com</a>

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
&lt;jkinney at localnetsolutions.com&gt;
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00311" href="msg00311.html">[ale] Auto increment in MySQL</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00298" href="msg00298.html">[ale] Auto increment in MySQL</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
<li><strong><a name="00301" href="msg00301.html">[ale] Auto increment in MySQL</a></strong>
<ul><li><em>From:</em> james.sumners at gmail.com (James Sumners)</li></ul></li>
<li><strong><a name="00303" href="msg00303.html">[ale] Auto increment in MySQL</a></strong>
<ul><li><em>From:</em> kafka at antichri.st (George Carless)</li></ul></li>
<li><strong><a name="00306" href="msg00306.html">[ale] Auto increment in MySQL</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00308.html">[ale] Auto increment in MySQL</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00310.html">[ale] Auto increment in MySQL</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00310.html">[ale] Auto increment in MySQL</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00311.html">[ale] Auto increment in MySQL</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00309"><strong>Date</strong></a></li>
<li><a href="threads.html#00309"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>