Subject | Re: Lock update for checkin/checkout? |
---|---|
Author | h_urlaf |
Post date | 2004-02-05T08:30:56Z |
--- In firebird-support@yahoogroups.com, Jakub Hegenbart
<Kyosuke@s...> wrote:
preferred? The dummy update, or the SELECT FOR UPDATE WITH LOCK?
Would I still need to SET TRANSACTION NO WAIT ISOLATION LEVEL READ
COMITTED when doing this?
The manual says that "SET TRANSACTION affects the default
transaction". Would that be the currently running transaction, or some
kind of default 'transaction template' that would affect the defaults
for all transactions created after the SET TRANSACTION?
Emiliano
<Kyosuke@s...> wrote:
> Oh, I wrote an unfinished sentence :)That actually sounds just like what I want to do... so which would be
>
> >....that once you SELECT
> >FOR UPDATE WITH LOCK that one particular row, you can safely convert
> >your BLOB to your heart's content and no other transaction will render
> >your CPU time...
> >
preferred? The dummy update, or the SELECT FOR UPDATE WITH LOCK?
Would I still need to SET TRANSACTION NO WAIT ISOLATION LEVEL READ
COMITTED when doing this?
The manual says that "SET TRANSACTION affects the default
transaction". Would that be the currently running transaction, or some
kind of default 'transaction template' that would affect the defaults
for all transactions created after the SET TRANSACTION?
Emiliano