Subject Re: Is it a feature or a bug of rows versioning?
Author vmdd_tech
Thanks for the explanation.

Using PowerBuilder, I tried SQLCA.lock = "RC" according to
its documentation, but it still did not work.

PowerBuilder allows me to pass a raw connect string to the
driver. Do you know what connect string to set isolation level
to READ COMMITED?

Ben


--- In firebird-support@yahoogroups.com, Doug Chamberlin >
> What you are seeing is the effect of a specific "Transaction
Isolation"
> setting which is being used. The results you are obtaining reflect
a
> transaction isolation setting of "repeatable read", or "snapshot".
This
> means that your transaction will always see the database as it was
when the
> transaction was started.
>
> To achieve what you want you need to change this to a transaction
isolation
> setting of "read committed" which means your transaction will see
the
> results of all other committed transactions as soon as they are
committed.
>
> Check the documentation on the middleware you are using (JDBC or
ODBC or
> other) to see how to change this setting.
>
> BTW, this is not really related to the existence of the versioning
engine
> at all. That's just the mechanism which is used to implement the
> transaction isolation rules. If it was not that, then some other
mechanism
> would have to be used to achieve the same results.