Bug #93787 | Auto-inc primary key field changes to 0 on update with ODBC > 5.3.4 | ||
---|---|---|---|
Submitted: | 2 Jan 2019 18:07 | Modified: | 14 Aug 2020 20:32 |
Reporter: | Brian Lowrance | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.3.9, 5.3.11, 8.0.13 | OS: | Windows (Server 2012 R2) |
Assigned to: | CPU Architecture: | Other (x64) |
[2 Jan 2019 18:07]
Brian Lowrance
[2 Jan 2019 18:12]
Brian Lowrance
Modifying "Version" field to indicate this affects releases after 5.3.4 (5.3.9, 5.3.11, 8.0.13).
[14 Jul 2020 20:32]
MySQL Verification Team
Please check version 8.0.21.
[15 Aug 2020 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[17 Mar 2021 10:45]
Simon Goodwin
I have just experienced the same problem. When I update any tables, all of which have primary keys with Auto Increment enabled, the primary key is written back to the database as 0. The ODBC Connector is chosen by my web host and I have no control over it. Can anyone advise on what I should do to get around this issue as I am totally stuck, being unable to complete a migration project on behalf of a client. My knowledge of MySQL is very primitive, being just enough to let me get by when making database-driven websites.