The problem I would face is that this still needs to be a sequential scan
in the table rather than an index lookup.
Regards,
Ed
On Tue, 14 Oct 2003, Arthur Ward wrote:
> > Is the rewrite only for the literal 'X = NULL' or will it do a test
> > against a value such as 'X = OLD.X' (and rewrite is OLD.X is NULL)?
> >
> > Is there any way to match NULLS to each other (as I am looking for a
> > literal row, not using NULL as the UNKNOWN). I suppose I could put in a
> > dummy value for the 'Not a valid value', but it seems to be quite awkward
> > when I really do want the NULL.
>
> I ended up writing an "equivalent" function for the project I'm working
> on. It goes like this in plpgsql:
>
> IF $1 IS NULL THEN
> RETURN $2 IS NULL;
> ELSIF $2 IS NULL THEN
> -- We already know $1 is not null.
> RETURN FALSE;
> ELSE
> -- Both args are not null.
> RETURN $1 = $2;
> END IF;
>
> That's the basic idea. I put a wrapper around this to generate a copy of
> it for all the data types used in my database.
>
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
