From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bug in on_error_rollback !? |
Date: | 2006-10-27 07:23:12 |
Message-ID: | 0A7E1F8ADA2DB302DC078260@[172.26.14.247] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On Freitag, Oktober 27, 2006 11:00:07 +0530 Gurjeet Singh
<singh(dot)gurjeet(at)gmail(dot)com> wrote:
> I was thinking of recommending this to someone, but wanted to try it on
> my own first; good thing that I did. I think it is broken as of now.
>
> I assume that the error thrown for 'select 1', inside a transaction, with
> 'on_error_rollback on', is not supposed to raise it's head !!!
>
> Or am I missing something?
>
[...]
You have to specify the parameter in upper case:
bernd(at)[local]:bernd #= BEGIN;
BEGIN
bernd(at)[local]:bernd #*= \set ON_ERROR_ROLLBACK
bernd(at)[local]:bernd #*= SELECT a;
ERROR: column "a" does not exist
LINE 1: SELECT a;
^
bernd(at)[local]:bernd #*= SELECT 1;
?column?
----------
1
(1 row)
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Zayats | 2006-10-27 07:41:05 | BUG #2724: Could not check connection status with "ssl=on" |
Previous Message | Gurjeet Singh | 2006-10-27 05:30:07 | bug in on_error_rollback !? |