On Aug 23, 2006, at 7:31 AM, <Christof(dot)Paal(at)nc3a(dot)nato(dot)int>
> Let us assume that the second statement fails because value 'b' is
> 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
> 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 jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
In response to
pgsql-bugs by date
|Next:||From: Klaus Ita||Date: 2006-08-26 22:40:42|
|Subject: Re: error in upper()|
|Previous:||From: Jim Nasby||Date: 2006-08-26 20:38:47|
|Subject: Re: Website issue|