[ psqlodbc-Bugs-1002386 ] 8.02.02.00 version ODBC driver does not show error message detail (regression)

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1002386 ] 8.02.02.00 version ODBC driver does not show error message detail (regression)
Date: 2007-03-16 00:31:54
Message-ID: 20070316003155.1ABFD2172D4@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Bugs item #1002386, was opened at 2007-03-02 13:41
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1002386&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Andrus Moor (kobruleht)
Assigned to: Nobody (None)
Summary: 8.02.02.00 version ODBC driver does not show error message detail (regression)

Initial Comment:
To reproduce, run update statement which causes fireign key violation error like

UPDATE mytable SET foreignkey='badvalue'

Observed:

ODBC driver returns error message without detail.

Expected:

Errorr returned from ODBC driver must contain also DETAIL: part which shows which foreign key constraint is violated like

DETAIL: Key (foreignkey)=(badvalue ) is not present in table "foo".

Note.

08.01.02 version of driver returns correct error message. DETAIL: part is present in message.

Enivronment:

8.02.02.00 version ODBC Unicode driver
Microsoft Visual FoxPro 9 SP1
PostgreSQL 8.1 on Windows XP

----------------------------------------------------------------------

>Comment By: Hiroshi Inoue (hinoue)
Date: 2007-03-16 00:31

Message:
Could you try the snapshot dll at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
?

regards,
Hiroshi Inoue

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1002386&group_id=1000125

Browse pgsql-odbc by date

  From Date Subject
Next Message David Bear 2007-03-16 00:43:58 kerberized odbc for windows
Previous Message Paul Lambert 2007-03-15 22:09:34 Re: Access violation - probably not the fault of Postgres