From: Tibor Laszlo <ltibor@mail.tiszanet.hu>
To: Gene Sokolov <hook@aktrad.ru>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ODBC not reporting RI violations.
Date: Wed, 19 Apr 2000 20:47:33 +0200
Message-ID: <00041920504200.01171@tir> (raw)
In-Reply-To: <13e801bfaa04$95bd5e70$0d8cdac3@aktrad.ru>
References: <13e801bfaa04$95bd5e70$0d8cdac3@aktrad.ru>
> PGSQL 7.0beta5, freebsd 4.0
> MS WinNT ODBC driver 6.50.00.00
>
> Seems like there is a problem in the way RI violations are reported through
> ODBC.
>
> If I execute the following query in psql, I get an error (which is correct):
>
> afmt=# INSERT INTO
> Orders(AccNum,Type,OpenTS,RefPosition,ItemID,IsBuy,Lots,OrdPrice,StpPrice,Lm
> tPrice,Expires)
> VALUES(1,1,'19 Apr 2000 15:17:46',0,4,1,1,104.30,0.,0.,'20 Apr 2000
> 00:00:00');
>
> ERROR: <unnamed> referential integrity violation - key referenced from
> orders not found in positions
>
> But if the same query is executed through ODBC, the error is not reported,
> the query just gets silently ignored. ODBC reports success, when in reality
> the query was aborted.
>
> All other errors are reported properly. This seems to be specific to RI
> violations.
>
> Gene Sokolov.
Yes. We reported the same things some weeks ago. Now there is a patch for
correcting this, I sent to Thomas, maybe found in current CVS in the ODBC
driver subtree. (Thomas is out of town for two weeks.) If urgent, we may send
the patch to the INTERFACES list.
Regards, Zoltan
(Tibor's friend)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ltibor@mail.tiszanet.hu, hook@aktrad.ru
Subject: Re: ODBC not reporting RI violations.
In-Reply-To: <00041920504200.01171@tir>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox