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 [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
