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

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

From: Kristis Makris <kristis(dot)makris(at)datasoft(dot)com>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Error messages not always reported through theODBCdriver -STATEMENT ERROR missing
Date: 2001-08-27 16:18:16
Message-ID: 200108271618.f7RGIMf48924@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Hiroshi,
 

> > ******************************************************************************************
> > 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 ?


I'm attaching two .sql files. Using psql, load the file "tables.sql" in
a fresh database. Then try to execute the commands in the "data.sql"
file. You should get the following error message:


test=# \i data.sql 
BEGIN
psql:data.sql:2: ERROR:  <unnamed> referential integrity violation - key
in tableb still referenced from tablea
COMMIT


If you try to issue the commands included in the "data.sql" file through
ODBC using VC++ (instead of psql) you will run across the case where an
exception cannot be captured.

Thanks,
-Kristis


Attachment: data.sql
Description: text/x-sql (48 bytes)
Attachment: tables.sql
Description: text/x-sql (498 bytes)

In response to

Responses

pgsql-odbc by date

Next:From: Ray DaigleDate: 2001-08-27 17:57:25
Subject: A problem with the nextval('') function
Previous:From: Cedar CoxDate: 2001-08-27 15:12:20
Subject: RE: Access 2000 ODBC table links

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