Bug #14260 auto_increment produces wrong values for unsigned integer columns
Submitted: 24 Oct 2005 14:59 Modified: 24 Oct 2005 15:12
Reporter: Amer Banet Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:3.1.10 OS:Windows (Windows XP SP2)
Assigned to: CPU Architecture:Any

[24 Oct 2005 14:59] Amer Banet 
Description:
I have the following column definition:

`ID` smallint(5) unsigned NOT NULL auto_increment

While inserting new records through JDBC the auto_increment function produces wrong values. More precisely it produces values that starts at 65536 in this case. This is the maximum column value + 1. Without the unsigned keyword the behavior is correct.

How to repeat:
see description

Suggested fix:
Don't use UNSIGNED auto_increment columns!
[24 Oct 2005 15:12] Mark Matthews 
This was fixed in 3.1.11 (which was released last week or so).