| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Ingo Ciechowski <ciechowski(at)cis-computer(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: WHERE <timestamp-val>=NULL malfunction in release 7.2 |
| Date: | 2002-06-21 17:13:42 |
| Message-ID: | 20020621171342.GA13170@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jun 20, 2002 at 17:28:31 +0200,
Ingo Ciechowski <ciechowski(at)cis-computer(dot)com> wrote:
> Hi,
>
> first of all let me tell all of you that PostgreSQL is among the best
> in OpenSource!
>
> Unfortunaly there's a (hopefully easy to fix) bug in release 7.2 and
> 7.2.1 that was not there in 7.1.3 and caused me to switch back today.
>
>
> Here's the table I'm using (unfortunately I already switched back to
> 7.1.3 and therefore can't verify whether or not this occurs with an
> easier setup):
7.1 had a hack because = NULL worked that way in Microsoft's DB.
You want to use 'IS NULL' to match null values. '= NULL' will always
be 'unknown' (which isn't 'true' so the where clause won't be satisified).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-21 17:15:56 | Re: WHERE <timestamp-val>=NULL malfunction in release 7.2 |
| Previous Message | Stephan Szabo | 2002-06-21 16:50:20 | Re: WHERE <timestamp-val>=NULL malfunction in release 7.2 |