Re: ERROR: Cannot insert a duplicate key into a unique index
От | Christopher Kings-Lynne |
---|---|
Тема | Re: ERROR: Cannot insert a duplicate key into a unique index |
Дата | |
Msg-id | ECEHIKNFIMMECLEBJFIGKEOGCBAA.chriskl@familyhealth.com.au обсуждение исходный текст |
Ответ на | ERROR: Cannot insert a duplicate key into a unique index (Haller Christoph <ch@rodos.fzk.de>) |
Ответы |
Re: ERROR: Cannot insert a duplicate key into a
|
Список | pgsql-hackers |
In our PHP app, we are also forced to parse error messages to get that kind of information. Register my vote for error codes (Tom Lane style...) Chris > -----Original Message----- > From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Haller Christoph > Sent: Thursday, 13 September 2001 7:18 PM > To: pgsql-hackers@postgresql.org > Subject: [HACKERS] ERROR: Cannot insert a duplicate key into a unique > index > > > [HACKERS] ERROR: Cannot insert a duplicate key into a unique index > > I'm working on a C code application using loads of > insert commands. > It is essential to distinguish between an error > coming from a misformed command or other fatal > reasons and a duplicate key. > In either case, the PQresultStatus() returns > PGRES_FATAL_ERROR > I can check PQresultErrorMessage() for the > error message above, but then I have to rely > on this string never be changed. > This is no good programming style. > Does anybody have another, better idea or is > there at least a header file available, where > all the error messages can be found? > > Regards, Christoph > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
В списке pgsql-hackers по дате отправления: