Subject | RE: [IBO] Transaction question |
---|---|
Author | Nico Callewaert |
Post date | 2001-03-23T08:04:19Z |
Geoff,
I'm using tiCommitted. So, if I understand you well, multiple users
can read records, while 1 user is updating.
Many thanks for your fast reply,
Nico Callewaert
-----Oorspronkelijk bericht-----
Van: Geoff Worboys [mailto:geoff@...]
Verzonden: vrijdag 23 maart 2001 9:04
Aan: IBObjects@yahoogroups.com
Onderwerp: Re: [IBO] Transaction question
users, in which case a deadlock can still occur when updates from
multiple users conflict.
Oh, actually it can appear. If you use Isolation=tiConsistency on
either transaction you effectively prevent updates to all records that
it reads. For this reason Isolation=tiConsistency is not recommended
unless this is exactly what you want to happen.
HTH
Geoff Worboys
Telesis Computing
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
I'm using tiCommitted. So, if I understand you well, multiple users
can read records, while 1 user is updating.
Many thanks for your fast reply,
Nico Callewaert
-----Oorspronkelijk bericht-----
Van: Geoff Worboys [mailto:geoff@...]
Verzonden: vrijdag 23 maart 2001 9:04
Aan: IBObjects@yahoogroups.com
Onderwerp: Re: [IBO] Transaction question
> My question now is, could a DEADLOCK appear in such a situation,Not from that user. But presumably your system will support multiple
> when a user is only READING information from a readonly
> transaction ?
users, in which case a deadlock can still occur when updates from
multiple users conflict.
Oh, actually it can appear. If you use Isolation=tiConsistency on
either transaction you effectively prevent updates to all records that
it reads. For this reason Isolation=tiConsistency is not recommended
unless this is exactly what you want to happen.
HTH
Geoff Worboys
Telesis Computing
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]