MySQL Bugs: #16132: concurrency violation

Bug #16132	concurrency violation
Submitted:	2 Jan 2006 19:21	Modified:	5 Feb 2006 21:49
Reporter:	Sean Wood	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	1.0.6	OS:	Windows (xp)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
database updates cause concurrency violation when values are defined as DOUBLE 

(IF AN INTEGER IS ENTERED THERE IS NO ERROR)

How to repeat:
  Dim adapter2 As New mysql.data.mysqlclient.mysqldataadapter()
    Dim CB2 As mysql.data.mysqlclient.mysqlcommandbuilder = New mysql.data.mysqlclient.mysqlcommandbuilder(adapter2)
    Dim myConnection2 As New mysql.data.mysqlclient.mysqlconnection()
    Dim dsdef As New DataSet()

  dsdef.Clear()
        Try
            myConnection2.ConnectionString = MainConnectString
            myConnection2.Open()
            Dim MyQuery As String = "Select * from PayRolldef"
            adapter2.SelectCommand = New mysql.data.mysqlclient.mysqlcommand(MyQuery, myConnection2)
            adapter2.Fill(dsdef)
        Catch e1 As Exception
            MsgBox(e1.Message & " Could not get payroll defaults")
            Return
        End Try

 Try
            adapter2.Update(dsdef)
        Catch e1 As DBConcurrencyException
            Dim customErrorMessage As String
            customErrorMessage += CType(e1.Row.Item(0), String)
            MessageBox.Show(customErrorMessage)
            MsgBox(e1.Message & " Could not Update Defaults")
            Return
        End Try

Sorry...I was not able to reproduce the bug. Could you please attach full text of your test case ?

I think he is talking about this problem, which I can confirm to be true for floats.

http://forums.mysql.com/read.php?38,28789

A concurrency violation is thrown because essentially the connector thinks the value of a float or double has changed, when in fact it has not.

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