From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | snpe <snpe(at)snpe(dot)co(dot)yu> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: problem with new autocommit config parameter and jdbc |
Date: | 2002-09-09 21:03:46 |
Message-ID: | 1031605427.268.160.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Mon, 2002-09-09 at 17:04, snpe wrote:
> I'm use 'autocommit=false' and have problem with psql
> When any commnad is lost, then next commnad get error for transactions
> (simple select command).BTW
>
> snpe> select * from org_ba;
> ERROR: relation org_ba does not exists
> snpe> select * from org_ban;
> ERROR: current transactions is aborted, queries ignored until end of
> transaction block
> snpe> rollback;
> ROLLBACK
> snpe> select * from org_ban;
Maybe I'm missing something, but isn't that the expected behaviour when
autocommit is turned off?
--
Rod Taylor
From | Date | Subject | |
---|---|---|---|
Next Message | snpe | 2002-09-09 21:04:38 | Re: problem with new autocommit config parameter and jdbc |
Previous Message | Laurette Cisneros | 2002-09-09 21:02:55 | Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | snpe | 2002-09-09 21:04:38 | Re: problem with new autocommit config parameter and jdbc |
Previous Message | Daniel Serodio | 2002-09-09 20:08:07 | Closing Statements and ResultSets |