Bug #6721 Timestamp problem error -7776 with MyDOBC 3.51 and ACCESS2000

• Submitted: 19 Nov 2004 13:32
• Modified: 5 Jan 2005 18:46
• Reporter: Francesco Costantini
• Status: Closed
• Category: Connector / ODBC
• Severity: S1 (Critical)
• Version: 4.1.7
• OS: Linux (Linux Fedora Core 3)
• CPU Architecture: Any

[19 Nov 2004 13:32] Francesco Costantini

Description:
Today I update mysql from 4.0.20 to 4.1.7.
I'm developing and application with a Fedora Core 3 Linux Server running MySQL and windowsXP SP2 with MyODBC driver 3.51 and MS ACCESS 2000.

With updated server I cannot update any table having timestamp field. (I use it as workaround for #delete# record problem in ACCESS 2000 as indicated in MyODBC documentation).
Can you help me ?

Thanx. (I'm sorry for my bad english writing)

How to repeat:
Create a table with a TIMESTAMP field. Try to update

[19 Nov 2004 17:06] Francesco Costantini

Using an SQL update query all is OK (also from ACCESS query) 

Example: 
UPDATE Sistema SET Sistema.Giornale_affari_progressivo = 33;

Using ACCESS table front end is KO !!!

[19 Nov 2004 18:31] Francesco Costantini

Updated also MyODBC windows Driver to 3.5.1.10
Still not working

[20 Nov 2004 9:28] Francesco Costantini

Solved ?

DB4Designer make create syntax like this (example):

CREATE TABLE TBL_causale_affare (
  ID_causale_affare INT(10) UNSIGNED ZEROFILL NOT NULL AUTO_INCREMENT,
  Descrizione CHAR(80) NOT NULL,
  Workaround TIMESTAMP NULL,
  PRIMARY KEY(ID_causale_affare)
)
ROW_FORMAT = fixed;

With MySQl 4.0.20 was OK

With MySQL 4.1.7 I have to remove NULL clause and use:
Workaround TIMESTAMP NOT NULL

I think it is by design...
Thanx

[5 Jan 2005 18:06] MySQL Verification Team

I assume you resolved the issue with the table schema. Isn't ?

[5 Jan 2005 18:31] Francesco Costantini

Yes i solved with a modified tabel design (setting NOT NULL field option)

[5 Jan 2005 18:46] MySQL Verification Team

Thank you for the update.