In perusing Microsoft’s Data Access Architecture guide I found a bit of a conundrum on concurrency. The document outlines 4 possible methods for updating data using a STDS.

1. Including only the primary key column
2. Including all columns in the WHERE claus
3. Including unique key columns and the timestamp column
4. Including unique key columns and the modified column

Of these four only the third one is really recommended by the document, but it also says that ADO.NET does not support this approach. We know that we want to use STDS in our project and it will exist in a disconnected data environment, and data integrity is paramount. So my question is do we have to implement this manually, or does someone have a “silver bullet” on this issue?

ADO.NET does support item 3 in your list. You select based on the primary
key WHERE the database timestamp is the same as the cached one. Am I missing
a point here ?


--
--------------------------------------------------------
Peter Wright (www.petewright.org)
Author of ADO.NET Novice To Pro
From Apress. www.apress.com (and 10
other doorstops from Wrox)


"Ed Curren" <(E-Mail Removed)> wrote in message
news:A51D7BA5-32A3-4DD6-BF2B-(E-Mail Removed)...
> In perusing Microsoft's Data Access Architecture guide I found a bit of a
conundrum on concurrency. The document outlines 4 possible methods for
updating data using a STDS.
>
> 1. Including only the primary key columns
> 2. Including all columns in the WHERE clause
> 3. Including unique key columns and the timestamp columns
> 4. Including unique key columns and the modified columns
>
> Of these four only the third one is really recommended by the document,
but it also says that ADO.NET does not support this approach. We know that
we want to use STDS in our project and it will exist in a disconnected data
environment, and data integrity is paramount. So my question is do we have
to implement this manually, or does someone have a "silver bullet" on this
issue?
>
>

No, you're not missing anything. After a second read the article was referring strictly to the CommandBuilder and Data Adapter Configuration Wizard. It's a non-issue. I just needed to slow down while reading it.