x = NULL

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: x = NULL
Date: 2001-09-10 14:24:20
Message-ID: Pine.LNX.4.30.0109101618010.680-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The x = NULL hack keeps biting people. Innocent people should not be
exposed to incorrect behaviour because of (supposed) MS Access breakage.
I strongly urge that we do one of the following:

1) Provide a tunable knob to turn this on (cf. KSQO)

2) Confine this to the ODBC driver somehow (which could be done via #1)

Actually, last time we discussed this there was some confusion whether
Access actually had the bug in question. That might be worth figuring
out.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Haroldo Stenger 2001-09-10 14:28:39 Re: Abort state on duplicated PKey in transactions
Previous Message Bruce Momjian 2001-09-10 14:17:02 Re: [HACKERS] to_char and Roman Numeral (RN) bug