Tom wrote:
> So I'm of the opinion that there's no good reason to change either our
> code or our docs. The standard-incompatibility is with BEGIN, not
> SET TRANSACTION, and it's already documented.
Yes.
> PS: the proposed patch is buggy as can be anyway: it applies the
change
> even if !doit, and it causes START TRANSACTION ISOLATION LEVEL xxx
> to affect not only the current but the next transaction, which surely
> cannot be justified by any reading of the spec ;-)
In IBM Informix the command SET TRANSACTION ISOLATION LEVEL xxx,
returns an error when issued outside a BEGIN WORK -- COMMIT transaction
block.
set transaction isolation level read uncommitted;
255: Not in transaction.
In their latest docs they state:
"The SET TRANSACTION statement complies with ANSI SQL-92."
So I agree that there is no need to change what we have.
Andreas