Subject | Re: [firebird-support] Re: FireBird locks |
---|---|
Author | Ann W. Harrison |
Post date | 2005-11-03T17:47:52Z |
chris_delphi wrote:
you used SELECT ...FOR UPDATE WITH LOCK which seems unlikely.
What it seems like is that the client is running a read committed
transaction with the options "no record versions" and "wait".
Since there's an uncommitted version, which the client can't see,
it waits.
the client to read the newest committed version rather than waiting
for the uncommitted version.
Regards,
Ann
>There's no such thing as a writable data set in Firebird, unless
> We have found a way to simpify and explain the bug though.
>
> So it looks to us as if our client app is trying to grab a writeable
> dataset rather than read only.
you used SELECT ...FOR UPDATE WITH LOCK which seems unlikely.
What it seems like is that the client is running a read committed
transaction with the options "no record versions" and "wait".
Since there's an uncommitted version, which the client can't see,
it waits.
> n.b. as a test if we run the same query in IB Expert while the serverIB Expert is using different options - specifically it allows
> is paused it will return the dataset and not lock.
the client to read the newest committed version rather than waiting
for the uncommitted version.
Regards,
Ann