| From: | Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no> |
|---|---|
| To: | "mascarm(at)mascari(dot)com" <mascarm(at)mascari(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-07 19:42:32 |
| Message-ID: | 86snhcm5zr.fsf@athene.i.eunet.no |
| 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. I'm
> sure this is how other vendors, like Oracle handle the issue. Well,
> probably sure... :-)
<applause>
That's the intelligent solution, of course.
-tih
--
The basic difference is this: hackers build things, crackers break them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-06-07 20:04:42 | Re: Re: 7.2 items |
| Previous Message | Oleg Bartunov | 2001-06-07 19:38:20 | Re: Re: 7.2 items |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Pilosov | 2001-06-07 19:51:38 | Re: Getting row with id=max(id) |
| Previous Message | Mike Mascari | 2001-06-07 19:36:20 | RE: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards |