Re: Error messages not always reported through the ODBCdriver -STATEMENT ERROR missing

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Kristis Makris <kristis(dot)makris(at)datasoft(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Error messages not always reported through the ODBCdriver -STATEMENT ERROR missing
Date: 2001-08-27 00:01:45
Message-ID: 3B898DE9.BD8B38F7@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2001-08-27 00:18:12 Re: Again, it doesn't compile :-)
Previous Message Johann Zuschlag 2001-08-26 18:51:25 Again, it doesn't compile :-)