Subject | Re: [firebird-support] FOR SELECT resultset changed during update statement |
---|---|
Author | Ann W. Harrison |
Post date | 2010-12-14T20:34:56Z |
On 12/14/2010 2:14 PM, Michael Ludwig wrote:
own changes. Paul Vinkenoog has a very good explanation of the
standard approach to cursor stability w/r/t a transaction's own
changes.
Good luck,
Ann
> Ann W. Harrison schrieb am 13.12.2010 um 18:36 (-0500):No, because normally a transaction even in Snapshot mode sees its
>> On 12/13/2010 6:48 AM, raivis83 wrote:
>>>
>>> I have noticed one problem with FOR SELECT statement in pl/sql
>>> procedure. Correct me if I am wrong but as far as I know ResultSet
>>> returned by SELECT statement should remain unchanged while looping
>>> through it. But it isn't.
>>
>
> Could Firebird's behaviour in this situation be explained as
> READ COMMITTED? And READ COMMITTED regardless of my transaction
> isolation setting?
>
own changes. Paul Vinkenoog has a very good explanation of the
standard approach to cursor stability w/r/t a transaction's own
changes.
Good luck,
Ann