> 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
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2000-04-05 14:46:50|
|Subject: Re: AIX and gcc (was: bug in nabstime.c)|
|Previous:||From: Jan Wieck||Date: 2000-04-05 11:50:43|
|Subject: Re: 7.0 FK trigger question|
pgsql-interfaces by date
|Next:||From: Bruce Momjian||Date: 2000-04-05 13:27:27|
|Subject: Programming Interfaces: EOAdaptor (fwd)|
|Previous:||From: Stefano Cracolici||Date: 2000-04-05 09:29:55|