Bug #9927 Updating datetime columns

Description:
When Microsoft Access 2000 is linked to a MyISAM table that has more than one datetime column, the last datetime column is not avaible for insert/update.

How to repeat:
mysql> CREATE TABLE teste (
    -> id int(11) NOT NULL auto_increment,
    ->   ident_es varchar(12) default NULL,
    ->   date_in timestamp(14) NULL,
    ->   date_out timestamp(14) NULL,
    ->   date_bug timestamp(14) NULL,
    ->   perceived_severity tinyint(4) default NULL,
    ->   info_ad1 varchar(80) default NULL,
    ->   info_ad2 varchar(80) default NULL,
    ->   permanencia int(10) default NULL,
    -> primary key(id)
    -> ) TYPE=MyISAM;

Link on Windows ODBC, than link on Access. After all, try to insert something on date_bug column.

You should only have one 'timestamp' field per table.
You want to use 'datetime' fields instead.

Multiple timestamp fields in one table should work. This bug needs to get re-verified with the latest release of Connector/ODBC.

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

Fix TIMESTAMP fields returned by SQLSpecialColumns

Attachment: bug9927.patch (text/plain), 3.32 KiB.

The fix for this bug has been committed to the source tree, and will be in 3.51.18.

Thanks for the bug report.

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.