pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ODBC not reporting RI violations.
2+ messages / 2 participants
[nested] [flat]

* ODBC not reporting RI violations.
@ 2000-04-19 13:38 Gene Sokolov <hook@aktrad.ru>
  2000-04-19 18:47 ` Re: ODBC not reporting RI violations. Tibor Laszlo <ltibor@mail.tiszanet.hu>
  0 siblings, 1 reply; 2+ messages in thread

From: Gene Sokolov @ 2000-04-19 13:38 UTC (permalink / raw)
  To: 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.






^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: ODBC not reporting RI violations.
  2000-04-19 13:38 ODBC not reporting RI violations. Gene Sokolov <hook@aktrad.ru>
@ 2000-04-19 18:47 ` Tibor Laszlo <ltibor@mail.tiszanet.hu>
  0 siblings, 0 replies; 2+ messages in thread

From: Tibor Laszlo @ 2000-04-19 18:47 UTC (permalink / raw)
  To: Gene Sokolov <hook@aktrad.ru>; +Cc: 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)



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2000-04-19 18:47 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-04-19 13:38 ODBC not reporting RI violations. Gene Sokolov <hook@aktrad.ru>
2000-04-19 18:47 ` Tibor Laszlo <ltibor@mail.tiszanet.hu>

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