Subject | Re: [ib-support] no_auto_undo (was Simple challenge) |
---|---|
Author | Ann W. Harrison |
Post date | 2002-11-02T21:41:46Z |
At 08:15 AM 11/3/2002 +1100, Peter Faulks wrote:
statements become start_transaction calls. Replace the SET
TRANSACTION statement with a start transaction call, as described
in the API manual. Check the output of gpre first so you use
the same handle name as the generated code.
There's a -m switch on gpre that says "I'm an adult and handle
my own transactions so don't do me any favors". Without it, gpre
generates a test before every DML or DDL statement, checking for
a connection and connecting if necessary, then testing for an
active transaction and starting one if necessary. That's a lot
of pure bloat - useful for children and careless programmers,
perhaps.
Regards,
Ann
www.ibphoenix.com
We have answers.
>So currently, the only way to set "no_auto_undo" is to use the API, andSure. Take a look at the output of gpre - the SET TRANSACTION
>not ESQL. Or is there a way around this?
statements become start_transaction calls. Replace the SET
TRANSACTION statement with a start transaction call, as described
in the API manual. Check the output of gpre first so you use
the same handle name as the generated code.
There's a -m switch on gpre that says "I'm an adult and handle
my own transactions so don't do me any favors". Without it, gpre
generates a test before every DML or DDL statement, checking for
a connection and connecting if necessary, then testing for an
active transaction and starting one if necessary. That's a lot
of pure bloat - useful for children and careless programmers,
perhaps.
Regards,
Ann
www.ibphoenix.com
We have answers.