|
|
Posted by dave Beseke on 07/06/05 16:21
I have a C# application that creates a SqlConnection object with an ADO
connection string and then sets up a SQlTransaction object for that
connection. Several records are posted to different tables in the
database within this transaction. All these tables uses an identity
element as their primary key. If the transaction fails, the records are
rolled back, but the identity elements are not reset. In other words,
if the last good record had an identity of 1000, and I roll back a
record that was assigned 1001, the next good record end up with an
identity value of 1002. I have not been able to find information as to
whether this behavior is by design, but it seems to me that if I do a
rollback, these identity elements should also be rolled back. Is this
behavior a bug?
*** Sent via Developersdex http://www.developersdex.com ***
Navigation:
[Reply to this message]
|