Best Practice for UpdateConcurrencyType?


Author
Message
Edhy Rijo
E
StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
Hi,

What would be the best option to use between the RowVersion and TimeStamp for checking the concurrency type and why?

Edhy Rijo

Reply
Trent Taylor
Trent Taylor
StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 7K
One other point here....if you actually wanted to include the concurrency field in any type of query, you are dealing with, as you said, binary data.  This becomes more difficult to include in queries if you are trying to determine something in regards to auditing, etc.  So if you were trying to filter out records to see only records that have been modified, then you would have to create a query using values like this:

SELECT COUNT(*) FROM MyTable WHERE MyTimeStampField <= 0x00000000000007D1

(Which obviously you would want to use a parm, but you get my point)

Versus using an integer value

SELECT COUNT(*) FROM MyTable WHERE MyTimeStampField <= 1

So anyway that I look at it...it is far easier to deal with an integer...at least in my simple world Tongue

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search