| Subject | Re: [firebird-support] Re: Checking periods don't overlap |
|---|---|
| Author | Dan Wilson |
| Post date | 2004-06-14T14:09:21Z |
On 6/14/2004 at 1:32 PM johnsparrowuk wrote:
Isn't this situation what the "snapshot table stability" isolation mode was designed to cover? IOW, if you used a read-committed transaction to perform your usual checks and interaction with the user, then when the user has given their final OK to save the data, start a new snapshot table stability transaction which performs one final check for conflicts then either save and commit or rollback. Or am I missing something obvious?
HTH,
Dan.
> Well, it's a option in SQL Server 2005 (turned off by default!). ForJohn,
> use when 'update conflicts are rare' according to the blurb.
> Maintained by using a linked list in tempdb (ewwwwww!).
>
> I'm prepared to accept FB is the coolest db ever! but...
>
> Just tell me how I can solve my period-overlap problem???!?!?! :0
>
> John
>
Isn't this situation what the "snapshot table stability" isolation mode was designed to cover? IOW, if you used a read-committed transaction to perform your usual checks and interaction with the user, then when the user has given their final OK to save the data, start a new snapshot table stability transaction which performs one final check for conflicts then either save and commit or rollback. Or am I missing something obvious?
HTH,
Dan.