Concurrency violation on mysql using VB.NET wizard table update

Question

0.00/5 (No votes)

See more:

On a DataGrideView connect to a MySQL Database, always I undo de changes of a field and I try to update exact as original info, I got an error "Concurrency violation: the UpdateCommand affected 0 of the expected 1 records"

It is a Single user application.

I load the data, I change a field then I put as loaded and ERROR.

my code:

VB

Me.Validate()
Me.TesteBindingSource.EndEdit()
Me.TesteTableAdapter.Update(Me.DataSetMySQL_TESTE.teste)

What I have tried:

If I changed the data in the field everything OK. But if the changes are equal as on loaded then error!

Posted 2-Mar-20 1:33am

RZ50

Updated 3-Mar-20 22:31pm

Maciej Los

v2

Add a Solution

Comments

[no name] 2-Mar-20 9:48am

Just have a look right in the CP page under "Related Questions". I think you will find an answer for this. Btw. looks not like a 'real error' it is more that 'Affected Records' returns '0' for the update.

Maciej Los 2-Mar-20 11:51am

What MySql driver are you using?

RZ50 2-Mar-20 11:59am

MySQL ODBC 5.1 Driver

Maciej Los 2-Mar-20 12:07pm

Is there any reason to use ODBC? I'd use MySQL Connector for .NET. See: MySQL - odbc - Should I use Connector/NET or Connector/ODBC to develop my application?[^]
What field causes such of error? I'm guessing that numeric...

RZ50 2-Mar-20 12:45pm

my table (test) is simple:
pk INT(11)
nome VARCHAR(45)

my CommandText:
UPDATE test SET nome =? WHERE (pk =?)

if I change the wrong record in the DataGridView and reset the initial information and then I change the correct record and when updating it gives me this error and I lose the information of the correct record...

Maciej Los 2-Mar-20 12:52pm

How do you reset information? What method are you using?

RZ50 2-Mar-20 13:01pm

With keyboard.
Pk nome
1 abc --> I changed to AB and then I delete with keyboard to stay the same abc
2 xyz --> I changed to AB this is to stay
after save give me the error on record 1 and lost the information of rec2

Maciej Los 2-Mar-20 13:27pm

Seems, you need to reject changes in the code, before you start another change.
Please, read this: Updating Data Sources with DataAdapters - ADO.NET | Microsoft Docs[^]

RZ50 3-Mar-20 12:41pm

After read your suggestion I found this note "This causes the rows affected count returned to be zero, which the DataAdapter interprets as a concurrency conflict. In this event, a DBConcurrencyException will be thrown."

So in my Driver I change the option "Return matched rows instead of affected rows" to true and the problem is SOLVED!

Thank you for all...

Maciej Los 3-Mar-20 16:39pm

Great! I suggest to post this as an answer (and accept it via green button) to remove your question from unanswered list.

2 solutions

Solution 1

According to our discussion in comments...

Please, read this: MySQL :: Concurrency violation problem on dataset update[^]

There's a suggestion:

Quote:
I ran into this. Switching DOUBLE to type DECIMAL(19,4) fixed it for me. Hope this helps somewhat.

Posted 2-Mar-20 6:14am

Maciej Los

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RZ50 · Accepted Answer · 2020-03-03T22:31:00

I found this note "This causes the rows affected count returned to be zero, which the DataAdapter interprets as a concurrency conflict. In this event, a DBConcurrencyException will be thrown."

So in my ODBC Driver I change the option "Return matched rows instead of affected rows" to true and the problem is SOLVED!