| From: | Edmund Dengler <edmundd(at)eSentire(dot)com> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Type conversions and nulls |
| Date: | 2004-05-11 23:50:19 |
| Message-ID: | Pine.BSO.4.58.0405111949010.28696@cyclops4.esentire.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ahh, thanks. So it is simply a syntactic transform, and not really a
"proper" internal comparison operator change.
Regards,
Ed
On Tue, 11 May 2004, Stephan Szabo wrote:
> Use the full version or if you're generating the query strings on the fly
> put only the check that matters (either the equality or the is null as
> appropriate for the values). Or if all you care about is true/false,
> possibly
> select exists(select 1 from tmp where ...)
> may be better.
>
> Transform_null_equals is meant convert a very specific x = NULL or NULL =
> x into x IS NULL. It doesn't (nor is it meant to) change how nulls
> compare.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2004-05-12 00:19:08 | Washintonians and Oregonians |
| Previous Message | Stephan Szabo | 2004-05-11 23:38:46 | Re: Type conversions and nulls |