Skip site navigation (1) Skip section navigation (2)

Re: PATCH: Integrity constraint violation should set SQLSTATE to 23000

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Chris Ingram" <cingram(at)intellisync(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: PATCH: Integrity constraint violation should set SQLSTATE to 23000
Date: 2005-10-04 19:04:28
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3175@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Chris Ingram [mailto:cingram(at)intellisync(dot)com] 
> Sent: 03 October 2005 23:04
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)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

Next:From: Joel FradkinDate: 2005-10-04 22:27:05
Subject: Just as an FYI We are up solid now on pgsql libpq version
Previous:From: Greg CampbellDate: 2005-10-04 13:34:14
Subject: Re: [ODBC] Unbound text box, Text > 255 characters, MSAccess/PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group