On Aug 23, 2006, at 7:31 AM, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
Let us assume that the second statement fails because value 'b' is
illegal.
Either the ODBC driver or the DBMS now rejects all follow-on queries
with the error message:
Error while executing the query;
ERROR: current transaction is aborted, commands ignored until
end of transaction block
I would have expected that it would still be possible to run queries
inside this transaction (in fact, the same code continues to run in
Sybase and MSSQL Server).
Otherwise it is not possible to write your own transaction logic or
your
own error handling in this environment.
Why continue to run commands if you're just going to roll them back?
In any case, I fail to see how this makes it impossible to control
transactions. Perhaps you need to look into savepoints?
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
