Subject | Re: Is it a feature or a bug of rows versioning? |
---|---|
Author | vmdd_tech |
Post date | 2004-02-23T22:38:57Z |
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 >
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 "TransactionIsolation"
> setting which is being used. The results you are obtaining reflecta
> transaction isolation setting of "repeatable read", or "snapshot".This
> means that your transaction will always see the database as it waswhen the
> transaction was started.isolation
>
> To achieve what you want you need to change this to a transaction
> setting of "read committed" which means your transaction will seethe
> results of all other committed transactions as soon as they arecommitted.
>ODBC or
> Check the documentation on the middleware you are using (JDBC or
> other) to see how to change this setting.engine
>
> BTW, this is not really related to the existence of the versioning
> at all. That's just the mechanism which is used to implement themechanism
> transaction isolation rules. If it was not that, then some other
> would have to be used to achieve the same results.