New version, but still error.

dqminh · Post by **dqminh** » Wed 04 Mar 2009 10:36

Thank you. I see your information about new beta version of dotConnect. Is it fix the bug in this topic?

AndreyR · Post by **AndreyR** » Wed 04 Mar 2009 11:28

Yes, it does.

dqminh · Post by **dqminh** » Wed 04 Mar 2009 12:26

Ok, one question and one bug:

1, I download the beta, so I have not the license? Because I login to customer area, there is not beta version.

2, Bug (affect with 5.0.22 and 5.20 beta)

If we have a table, and in the column Name it allow null. Fist, we insert some item (Name still null). Second, query the item with Name is null -> ok. Third, update ANY row which has at least one column has null value with new value -> error.

Code: Select all

var db = new PartDataContext();

gv1.DataSource = db.Accessories.Where(p => p.VietnamName == null);
gv1.DataBind(); // ok, so many item

var o = db.Accessories.Single(p => p.AccessoryId == 41);
o.VietnamName = "abc";
db.SubmitChanges(); // DB concurrency violation

AndreyR · Post by **AndreyR** » Wed 04 Mar 2009 16:02

This Beta is trial only.
Could you please send me(support * devart * com, subject "LINQ: DbConcurrency") a small test project to reproduce the described problem?
I can't reproduce it on my environment.

dqminh · Post by **dqminh** » Mon 23 Mar 2009 04:45

Sorry because I cannot figure the problem. But I found the same problem with devart tool for vs 2008: sometime when I open the table in vs 2008, edit the data and update, the devart database developer tools say: Update operation affected 0 records due to possible concurrency violation, very similar with the bug in linq. In this case, if I close the edit window, re-open and edit again, it run ok.

AndreyR · Post by **AndreyR** » Mon 23 Mar 2009 12:27

Could you please send me the script of your table?
As an alternative, you can look through your DataContext's Log property and find the problem in the generated SQL.