Thread: Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards

Mike Mascari <mascarm@mascari.com> writes:
> The best solution would be to have the ODBC translate instances of '= 
> NULL' into IS NULL before submitting the query to PostgreSQL.

Does Access only talk to Postgres via ODBC?  (Seems plausible, but I
don't know.)  What about people copying-and-pasting queries generated
by Access; is it even possible?

I doubt that this'd really help much, in any case; it merely moves the
necessary switch from the backend to ODBC.
        regards, tom lane

Tom,

> Does Access only talk to Postgres via ODBC?  (Seems plausible, but I
> don't know.) 
Yes.
What about people copying-and-pasting queries generated
> by Access; is it even possible?

Yes, but MS Access uses some much non-standard SQL that "= Null" would
hardly be the only problem (try to build an UPDATE ... FROM in Access)

> I doubt that this'd really help much, in any case; it merely moves
> the
> necessary switch from the backend to ODBC.

Yes, but it does avoid cluttering up the PgSQL source with switches that
are only useful to a handful of users.

-Josh


______AGLIO DATABASE SOLUTIONS___________________________                                      Josh Berkus Complete
informationtechnology      josh@agliodbs.com  and data management solutions       (415) 565-7293 for law firms, small
businesses       fax 621-2533   and non-profit organizations.      San Francisco