Re: PATCH: Integrity constraint violation should set SQLSTATE to 23000 - Mailing list pgsql-odbc

From Dave Page
Subject Re: PATCH: Integrity constraint violation should set SQLSTATE to 23000
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3175@ratbert.vale-housing.co.uk
Whole thread Raw
List pgsql-odbc

> -----Original Message-----
> From: Chris Ingram [mailto:cingram@intellisync.com]
> Sent: 03 October 2005 23:04
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: RE: [ODBC] PATCH: Integrity constraint violation
> should set SQLSTATE to 23000
>
> Thanks for pointing out a much better way to address the
> problem, Dave.
>
> I've attached a patch that uses the SQLSTATE from the backend any time
> the error condition after executing a query is
> STMT_ERROR_TAKEN_FROM_BACKEND.  Besides solving the problem I
> reported,
> this seems to make much more sense than setting the SQLSTATE
> arbitrarily
> to HY000 "General Error" in this situation.  I look forward to your
> feedback.

Thanks Chris - patch applied.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Greg Campbell"
Date:
Subject: Re: Unbound text box, Text > 255 characters, MSAccess/PostgreSQL
Next
From: "Joel Fradkin"
Date:
Subject: Just as an FYI We are up solid now on pgsql libpq version