Re: Error messages not always reported through the ODBCdriver -STATEMENT ERROR missing - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: Error messages not always reported through the ODBCdriver -STATEMENT ERROR missing
Date
Msg-id 3B898DE9.BD8B38F7@tpf.co.jp
Whole thread Raw
In response to Error messages not always reported through the ODBC driver - STATEMENT ERROR missing  (Kristis Makris <kristis.makris@datasoft.com>)
Responses Re: Error messages not always reported through the ODBCdriver -STATEMENT ERROR missing  (Kristis Makris <kristis.makris@datasoft.com>)
List pgsql-odbc
Kristis Makris wrote:
>
> Hello Again,
>
> I've also tried the following from the psql command-line client:
>
> ******************************************************************************************
> wats=# begin;
> BEGIN
> wats=# select vendor_remove(1);
> ERROR:  <unnamed> referential integrity violation - key in vendor still
> referenced from vendorforwellagreement
> wats=# commit;
> COMMIT
> ******************************************************************************************
>
> psql reports the error when I issue the SELECT statement, not when I
> issue the commit. Shouldn't I be able to capture an exception when I do
> an ExecuteSQL() from VC++, instead of a CommitTrans() ?

Could you show me a reproducible example ?

regards,
Hiroshi Inoue

pgsql-odbc by date:

Previous
From: "Johann Zuschlag"
Date:
Subject: Again, it doesn't compile :-)
Next
From: Hiroshi Inoue
Date:
Subject: Re: Again, it doesn't compile :-)