Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards

From: "Joe Conway" <joe(at)conway-family(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards
Date: 2001-06-08 15:01:49
Message-ID: 003801c0f02b$f2be1f60$d7d310ac@jecw2k1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> We do not currently have correct implementations of IS TRUE, IS FALSE,
> or IS UNKNOWN (IS TRUE/FALSE are in there but give the wrong result
> for null inputs). This is on my to-do list to fix; not sure if the
> master TODO list mentions it or not. Actually it'd be a good project
> for a newbie hacker who wants to learn about the backend's
> expression-handling machinery. Anyone want to take it on?
>

I'd like to finish up the has_table_privilege function over the next week or
so and then take this on. Can you point me in a direction to start looking?

Thanks,

Joe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-06-08 15:04:26 Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards
Previous Message Tom Lane 2001-06-08 15:01:26 Re: Can the backend return more than one error message per PQexec?