Bug #56209 SQLColumns() returns bad NULLABLE value for AUTO_INCREMENT columns
Submitted: 24 Aug 2010 4:46 Modified: 8 Sep 2010 16:32
Reporter: Federico Omoto Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Documentation Severity:S2 (Serious)
Version:5.1.6 OS:Windows (Tested on Windows, maybe other OSes too)
Assigned to: Tony Bedford CPU Architecture:Any

[24 Aug 2010 4:46] Federico Omoto 
Description:
When you call SQLColumns() for a table column that is AUTO_INCREMENT, the NULLABLE column of the result set is always SQL_NULLABLE (1).

How to repeat:
Just call SQLColumns() for any table column that is AUTO_INCREMENT and you'll see that the NULLABLE column of the result set is always SQL_NULLABLE (1).
[24 Aug 2010 6:42] Tonci Grgin 
Federico, this should be a duplicate... Let me search.
[24 Aug 2010 7:25] Tonci Grgin 
As reported in Bug#3857 (and many other reports), this is not a bug...

Quoting Timothy:
This is because MySQL reports the DEFAULT value for such a column as NULL. It means, if you insert a NULL value into the column, you will get the next integer value for the table's auto_increment counter.

Tony, please document this fact so there are no more misunderstandings.
[8 Sep 2010 16:32] Tony Bedford 
The information has been added to the documentation XML sources.