MySQL Bugs: #12524: batchupdate probleme with real number

Bug #12524	batchupdate probleme with real number
Submitted:	11 Aug 2005 13:19	Modified:	30 May 2013 7:37
Reporter:	Sébastien Gariépy	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	MyODBC 3.51.11 MySQL 4.1.13	OS:	Windows (Windows XP sp2 french)
Assigned to:		CPU Architecture:	Any

Description:
When we use updatebatch in vb, we sometime have the error 80040E38. When we investigate on this error, we find that is when a number with decimal the update query in odbc fail with this error. With number with no decimal the query was successfull. We think that the decimal character used when ODBC make the update query is a comma and not a point. We know that MySQL engine accept just point.

We found that when we create a record line with no decimal and after we use decimal for updates, we have no problems. But if we create a line with decimal, we have the bug always.

How to repeat:
On windows XP in french. Make table with some float or double number and a primary key. Enter some lines of number with decimal. In vb make a connection with Option 3 and (adUseClient, vb). Make a recordset (Select * from Your_Table) with adOpenStatic, adLockBatchOptimistic. Change some value in the recordset and call your_recordset.updatebatch. You have the Microsoft Cursor Engine error '80040e38' ==> Row cannot be located for updating. Some values may have been changed since it was last read.

If we create lines with no decimal and make updates with decimals we don't have the bug.

We always have the bug if we create lines with decimal

Suggested fix:
We know that the bug is with decimal. We don't know if it the comma (,) or if it the addnew line with decimal. We are mystified...

Hi!

I was unable to reproduce this bug with the information you provided.  Can you please create a test-case that successfully reproduces this behaviour and upload it to this bug report ?

Thanks!

I update the server to version 4.1.13a and the problem seems to be different. Some batchupdate pass with no error and other crash with error 80040E38. It seems that problem occurred with number with decimal. Because the complexity of the source code, I have to make other simplest source to reproduce the behaviour. I will send it as soon as possible.

Thanks

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.