Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de
	[53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id IAA82026
	for <pgsql-hackers@postgresql.org>; Wed, 5 Apr 2000 08:33:09 -0400 (EDT)
	(envelope-from wieck@debis.com)
Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-hackers@postgresql.org
	id m12con4-0003knC; Wed, 5 Apr 100 14:20 MET DST
Message-Id: <m12con4-0003knC@orion.SAPserv.Hamburg.dsh.de>
From: wieck@debis.com (Jan Wieck)
Subject: Re: [INTERFACES] refint doesn't work well with BDE (fwd)
In-Reply-To: 
 <Pine.LNX.4.05.10004051126130.4358-100000@pc10.radnoti-szeged.sulinet.hu>
	from Kovacs Zoltan Sandor at "Apr 5, 2000 11:33:12 am"
To: Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu>
Date: Wed, 5 Apr 2000 14:20:10 +0200 (CEST)
CC: wieck@debis.com, pgsql-hackers@postgresql.org
Reply-To: Jan Wieck <wieck@debis.com>
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200004/106

> Hi Jan, refint error reporting seems to have a bug. The Windows ODBC
> driver cannot detect that refint machine dropped an error (I think that
> the same behaviour can be reproduced with the Unix ODBC driver, too). I
> suspect that the 7.0 refint manager's error string has an extra \n
> character (I found a lonely apostrophe at the beginning of a row in the
> log). beta3 has the same problem. What's your opinion? Regards, Zoltan
>
> ---------- Forwarded message ----------
> [...]
>
> BDE says nothing to this. BDE thinks that everything is all right, it changes
> the table (inserts a row). After making a refresh, one can realize that no
> changes were made, of course.
>
>
> Could you please help?

    I'm in no way an ODBC or BDE guy - anyway.

    First of all, 6.5.* didn't had the FOREIGN KEY implementation
    your 7.0 message is coming from. It's completely new stuff.

    Second, since an ERROR is correctly reported (violating a  RI
    constraint  is an ERROR and I cannot see any extra \n there),
    the bug seems to be in the ODBC or BDE part, not  looking  at
    the  return  code  but  trying to interpret the textual error
    message.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #