From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
---|---|
To: | "Little, Doug C" <Doug(dot)Little(at)vend(dot)frb(dot)org>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] psql sqlstate return code access |
Date: | 2015-03-18 07:37:30 |
Message-ID: | CAKoxK+5FtKi7c6WXDF5a9t9Rk3=CWBnduTA6GDfy3Xa4Me1aJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
Ciao,
On Tue, Mar 17, 2015 at 4:51 PM, Little, Doug C
<Doug(dot)Little(at)vend(dot)frb(dot)org> wrote:
> However, I could use a generic wrapper - but I don't think the customer would like this.
That's a solution, but I still have some doubts about the final aim.
First of all, for a successful statement there is sqlstate = 0 and no
exception. And what is the point of seeing a successful statement?
Does it suffice to know if the transaction has been committed or not?
That would be a lot easier, for example, from a program point of view.
Similarly, knowing the sqlstate of a wrong statement what information
adds for later analysis (because storing it into a table means that to
me)?
I believe there is something unclear in the design of the whole idea.
However, I would go for a wrapper.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Glyn Astill | 2015-03-18 10:43:19 | Re: Reg: PL/pgSQL commit and rollback |
Previous Message | Craig Ringer | 2015-03-18 02:11:46 | Re: pgpool + BDR, is it possible? |
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Ferrari | 2015-03-18 07:40:31 | Re: Keeping track of updates/performances |
Previous Message | Romain Billon-Grand | 2015-03-17 18:21:43 | Re: Keeping track of updates/performances |