Re: Non-skipping IDs with Master-Detail
- From: Brian Bushay TeamB <BBushay@xxxxxxxxx>
- Date: Sun, 23 Oct 2005 19:02:55 -0500
>Also, the order number (master ID) CANNOT SKIP, so from what I
>read, I'm only supposed to set the next key right before
>UpdateBatch to minimize conflicts in a multi-user environment.
>
>I issue a BeginTransaction right before calling my GetNextKey
>function (which also increments the key). This way, if the user
>aborts the order, everything gets rolled back at once.
There is not much worse that you can do to create problems on an SQL server than
to leave transactions open while a user has control of your application.
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- Follow-Ups:
- Re: Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Re: Non-skipping IDs with Master-Detail
- References:
- Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Non-skipping IDs with Master-Detail
- Prev by Date: Re: Non-skipping IDs with Master-Detail
- Next by Date: Re: changing a Clinet/Server application to use connection pooling
- Previous by thread: Re: Non-skipping IDs with Master-Detail
- Next by thread: Re: Non-skipping IDs with Master-Detail
- Index(es):
Relevant Pages
|