From: | Edmund Dengler <edmundd(at)eSentire(dot)com> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SET within a function? |
Date: | 2003-10-14 02:49:28 |
Message-ID: | Pine.BSO.4.58.0310132247160.12650@cyclops4.esentire.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Regards!
Ed
On Mon, 13 Oct 2003, Bruno Wolff III wrote:
> On Mon, Oct 13, 2003 at 21:16:33 -0400,
> Edmund Dengler <edmundd(at)eSentire(dot)com> wrote:
> >
> > I think if I could do a 'SET TRANSFORM_NULL_EQUALS TO ON' then this might
> > fix the issue (don't know, haven't tried it yet). My question is: can this
> > be done within a function such that at the end of the function, the value
> > is reset back to value upon entering (kind of like 'SET LOCAL' except for
> > just the length of the function call). Is this possible?
>
> I don't think that will do what you want. That setting is used to
> rewrite = null as is null, not to change things so that nulls match each
> other.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Phil Howard | 2003-10-14 04:25:48 | spam or crazy mail server changes? |
Previous Message | Bruno Wolff III | 2003-10-14 02:17:52 | Re: SET within a function? |