Bug #39961 Using ADO Recordset and Update to set Decimal field causes wrong value

Submitted:	9 Oct 2008 19:29	Modified:	21 Nov 2008 15:11
Reporter:	Meelis Lilbok	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	5.1.5	OS:	Any
Assigned to:	Jess Balint	CPU Architecture:	Any

Description:
Seting ADO Recordset decimal field value to 44.56 cause wrong value 445600.0000

How to repeat:
Dim r As New Recordset
r.open "select * from kogud where id=1", "dsn=mysql", adOpenKeyset, adLockBatchOptimistic, adCmdText
r.fields("m1").Value = 44.56
r.Update

Result - m1= 445600.0000

SQL Trace Log

Attachment: sql.log (application/octet-stream, text), 134.70 KiB.

SHOW CREATE table

Attachment: create table.txt (text/plain), 1.79 KiB.

ODBC 5.1.1 Windows, MySQL Server 5.1(Windows) and 5.0.32-Debian_7etch6-log

Verified using server side cursor. Client cursor not affected.

Code pushed to:
https://code.launchpad.net/~myodbc-developers/myodbc/bug39961

Pushed as rev 812, will be released in 5.1.6.

An entry was added to the 5.1.6 changelog:

Setting the ADO Recordset decimal field value to 44.56 resulted in an incorrect value of 445600.0000 being stored when the record set was updated with the Update method.

Bug#42316 was marked as a duplicate of this.

Bug#46162 was marked as duplicate of this report.

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.