Addendum- MS is indeed planning a fix... see
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1179601&SiteID=1 ... the response from MS is at the end of Page 1 plus several useful responses on Page 2.
I'd be very interested to hear how others are managing change tracking and concurrency in a multi tiered NET scenario. If they';re simply returning datasets back to a SP for handling, what happens if 2 users are making changes at once? E.g. one user changes customer address while the other user changes phone number. The first user updates. When the second user updates, how do you prevent overwriting of the newly updated address with the old value? If you're going to pass around objects or entities, surely they need to carry with them change tracking information, or be limited to values that have actually changed. Intriguing. Hopefully somebody can enlighten me.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1