About UpdateCheck attribute and Batch Updates

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

About UpdateCheck attribute and Batch Updates

Post by crazypit » Thu 20 Jan 2011 09:34

Hello,

You mention in your help file, that in order for an update to participate in a batch update, all properties should be marked as UpdateCheck = Never. Does this also apply to the Primary Key property? In fact, what is the purpose of this attribute on a Primary Key column? I guess all updates are performed checking that the primary key property has not changed its value...

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Thu 20 Jan 2011 16:41

Actually, changing the Update Check property for entity key will not affect generated commands, and the key will always participate in the WHERE clause. Thank you for your report, we will consider disabling this property for entity keys.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Thu 20 Jan 2011 16:52

Ok, how does that affect Batch Updates? do i still need to change the Update Check to Never even for the primary keys?

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Fri 21 Jan 2011 18:18

Setting the 'Update Check' property to other value than 'Never' does not disable batch updates. Actually, changing this property should have no effect at all for entity keys, and will be disabled for them in one of the nearest builds.

To check whether batch updates were used, you can, e.g., view the DataContext log. If they were, commands should be grouped, and their parameters should be specified below in a single list. If they weren't, parameters for each command will be described just after this command.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Thu 10 Feb 2011 17:48

We have disabled the 'Update Check' property for key fields, now it cannot be set to a value other than 'Always'. This change is available in the new 6.10.103 build of dotConnect for Oracle. The new build can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

For the detailed information about the fixes and improvements available in dotConnect for Oracle 6.10.103, please refer to
http://www.devart.com/forums/viewtopic.php?t=20224

Post Reply