Re: ODBC not reporting RI violations. - Mailing list pgsql-interfaces

From Tibor Laszlo
Subject Re: ODBC not reporting RI violations.
Date
Msg-id 00041920504200.01171@tir
Whole thread Raw
In response to ODBC not reporting RI violations.  ("Gene Sokolov" <hook@aktrad.ru>)
List pgsql-interfaces
> 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)


pgsql-interfaces by date:

Previous
From: John David Garza
Date:
Subject: Re: Large strings
Next
From: Arkin
Date:
Subject: Re: Is this usage correct ?