| Subject | Re: Advancing the OAT |
|---|---|
| Author | Stephen Boyd |
| Post date | 2005-12-05T22:02:45Z |
--- In firebird-support@yahoogroups.com, Ivan Cruz <ivan@a...> wrote:
1) I would still have the read transaction open for the entire duration
so I would still have a stuck OAT.
2) I am uncertain how locking would be affected.
3) For reasons of convenience I read the row to be updated and then use
RDB$KEY in the UPDATE statement to find the record for update. This
won't work across multiple transactions.
> Firebird supports an (unlimited?) number of transactions in "paralel",Several reasons.
> inside a session. Why not process your updates in another transaction?
>
> Ivan.
>
1) I would still have the read transaction open for the entire duration
so I would still have a stuck OAT.
2) I am uncertain how locking would be affected.
3) For reasons of convenience I read the row to be updated and then use
RDB$KEY in the UPDATE statement to find the record for update. This
won't work across multiple transactions.