| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "mascarm(at)mascari(dot)com" <mascarm(at)mascari(dot)com> |
| Cc: | "'Tom Ivar Helbekkmo'" <tih(at)kpnQwest(dot)no>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Mark Stosberg <mark(at)summersault(dot)com>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards |
| Date: | 2001-06-08 15:04:26 |
| Message-ID: | 9679.992012666@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Mike Mascari <mascarm(at)mascari(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-06-08 15:09:40 | Re: Need information about Foreign Key created Triggers |
| Previous Message | Joe Conway | 2001-06-08 15:01:49 | Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Bartlett | 2001-06-08 15:26:57 | Re: maximum number of rows in table - what about oid limits? |
| Previous Message | Tom Lane | 2001-06-08 14:53:05 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |