Dave Cramer <pg@fastcrypt.com> writes:
> If you really want this behaviour then
> set
> transform_null_equals = off to on
> in postgresql.conf
Don't think that will help him --- that kluge just causes "foo = NULL"
to be translated to "foo IS NULL" *when the NULL is written as a
literal constant*. He seems to want a null passed through a parameter
symbol to be treated as a normal comparable value. The short answer
is that you can't do that in SQL; better rethink your usage of NULL,
because it hasn't got the behavior you want.
regards, tom lane