From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Konstantin Izmailov <pgfizm(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Is there a logical reason for 25P02? |
Date: | 2010-10-05 11:13:32 |
Message-ID: | 4CAB085C.5030106@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/05/2010 12:39 PM, Konstantin Izmailov wrote:
> Howdy,
> I've noticed that there is a difference in result of execution of the
> following statement:
> INSERT INTO testtable(col1) VALUES(NULL);
> depending on whether the command is prepared or not.
>
> If I call PQprepare/PQexecPrepared for the statement, the error
> "transaction aborted" is returned with SQL State = "25P02".
Specifically, I suspect the message should be:
ERROR: current transaction is aborted, commands ignored until end of
transaction block
If that's what you're getting, the problem was with an earlier command
that returned an error you didn't notice, not with the command you just
ran. I'm unsure if this could cause PQexecPrepared to return sqlstate
25P02 if PQprepare fails, but would want to investigate the possibility.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2010-10-05 11:19:12 | Re: Trying to figure out why these queries are so slow |
Previous Message | Thom Brown | 2010-10-05 11:09:01 | Re: Trying to figure out why these queries are so slow |