Peter Whittleton wrote:
>
> Anyone used SET TRANSACTION (or SET ISOLATION LEVEL) to change the
> isolation level of a transaction? The docs state that '... after
> a COMMIT WORK statement completes the transaction or a ROLLBACK WORK
> statement cancels the transaction, the isolation level is reset to
> the default.'
That's right.
> This doesn't seem to be happening.
>
> For example ...
>
> - my default isolation is committed read
> - from dbaccess I run:
> begin work;
> set transaction isolation level repeatable read;
> select count(*) from tbl_name;> commit work;
> - onstat -g sql shows iso lvl as RR (repeatable read), so the commit
> has *not* reset to the default.
>
> Anyone seen this behaviour before. Are the docs wrong, or is this
> a 7.12 bug.
But -g sql shows you your sql commands. The isolation level at that
time WAS RR. If you run another sql command and check the level it
will be CR.
Hope that helps,
--
Mark.
+------------------------------------------------------------------+
|Mark D. Stock - The West Solutions Group http://www.west.co.za |
| The Informix FAQ is at http://www.iiug.org |
|mailto:marks@west.co.za +-----------------------------------------+
|Tel: +27 11 803 2151 |If it doesn't work, force it! |
|Fax: +27 11 803 2189 |If it breaks, it needed replacing anyway!|
|Cell: +27 83 250 2325 |Well, that's how I code anyway! |
+------------------------+-----------------------------------------+