Re: read consistency question

From: Tanel Poder <tanel_at_@peldik.com>
Date: Thu, 24 Jul 2003 20:05:40 +0300
Message-ID: <3f2011e5$1_1@news.estpak.ee>

Hi!

Yep, you're probably right. You have to verify that your serializable transaction deals only with data which isn't modified meanwhile by other transactions (including inserts). I did a little testing in PL/SQL and setting transaction serializable + opening for update cursor + deleting from cursor afterwards works as excpected, that no newly inserted rows are seen and only original ones are deleted. Newly inserted rows appear after commit is done on serializable transaction.

Tanel.

> This (as I understand it) is the correct behaviour for serializable
> transactions.
> I do not believe we are seeing a bug here.
> It is the type of isolation the OP requires and the 8177 error is telling
> him
> that a rollback/restart transaction is required. It may well be that due
to
> the
> high concurrency session A will never succeed and a different approach is
> required.
>
> HTH
>
> eric
>
> --
> Remove the dross to contact me directly
>
>
Received on Thu Jul 24 2003 - 12:05:40 CDT