MySQL Bugs: #11791: Problem Updaing DATETIME fields in innodb tables.

Bug #11791	Problem Updaing DATETIME fields in innodb tables.
Submitted:	7 Jul 2005 8:37	Modified:	28 May 2013 10:49
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	MySQL Server v4.1.12a	OS:	Windows (XP sp2)
Assigned to:		CPU Architecture:	Any

Description:
Exception Error Message:
"row cannot be located for updating some values may have changed since it was last read"

I'm using MyODBC v3.51.11-2
MySQL Server v4.1.12a
Using ADO to interface between C# and MyODBC.
Tables are INNODB type
I have the DNS setting "Return Matching Rows" on.

The problem only occurs with Updating a DATETIME field using the ado UPDATE function on a specific record.

It is not an option to use the .net connector as i have to be able to interface to any type of database.

The moethod im using to update is:
1: Open RecordSet
2: Find Specific record(using ADO Find method on the primary key)
3: Update all fields individually using ADO Update command.

Now I can have an innodb table of 10 fields of varying types but none of which are DATETIME and this can be done fine. The problem occurs on the first DATETIIME field it comes too and my app throws an exception with the above error.

The problem is not my datetime string as this method works fine for non innodb tables with the same data.

I've tried various versions of MySQL and MyODBC to try and find where the problem is occurring but to no avail.

Does anyone know if this is a known issue or of a workaround. Ive been stuck on this problem for some time now and cannot find a way around it.

How to repeat:
The moethod im using to update is:
C# and ADO to MyODBC connector (versions above)
1: Open RecordSet
2: Find Specific record(using ADO Find method on the primary key)
3: Update all fields individually using ADO Update command.

DATETIME fields throws the exception:
row cannot be located for updating some values may have changed since it was last read

Hi!

I was unable to reproduce this bug.  Can you please upload a fully working C# test case that successfully reproduces it ?

Thanks

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".

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.