Bug #9927 | Updating datetime columns | ||
---|---|---|---|
Submitted: | 15 Apr 2005 12:19 | Modified: | 3 Aug 2007 10:11 |
Reporter: | Alexandre Dias | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51 | OS: | Windows (Windows 2000) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
[15 Apr 2005 12:19]
Alexandre Dias
[29 Apr 2005 1:33]
Daniel Kasak
You should only have one 'timestamp' field per table. You want to use 'datetime' fields instead.
[28 Mar 2007 19:24]
Jim Winstead
Multiple timestamp fields in one table should work. This bug needs to get re-verified with the latest release of Connector/ODBC.
[2 Apr 2007 9:45]
Tonci Grgin
Verified as described with: - MySQL server 5.0.38BK on WinXP Pro SP2 localhost - MyODBC 3.51.14 GA - MS Access 2003 (11.6566.8122) SP2 - JET engine: msjet40.dll, 4.00.8618.0 / 2004-04-16 - Submitted table structure
[26 Jul 2007 17:04]
Jim Winstead
Fix TIMESTAMP fields returned by SQLSpecialColumns
Attachment: bug9927.patch (text/plain), 3.32 KiB.
[30 Jul 2007 15:30]
Jim Winstead
The fix for this bug has been committed to the source tree, and will be in 3.51.18. Thanks for the bug report.
[3 Aug 2007 10:11]
MC Brown
A note has been added to the 3.51.18 changelog: When using a table with multiple TIMESTAMP columns, the final TIMESTAMP column within the table definition would not be updateable.