From: | "Picard, Cyril" <cyril(dot)picard(at)eads-dsn(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | RE: passing null parameter to plpgsq functions |
Date: | 2001-04-03 09:39:30 |
Message-ID: | B5CDCF382265D311BF33009027A8FE9401E6F369@pmrmsg.edsn.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Thank you ! I planned to use the 7.1 to get the outer join capability.
Is the 7.1 stable ?
> -----Message d'origine-----
> De: Richard Huxton [SMTP:dev(at)archonet(dot)com]
> Date: mardi 3 avril 2001 10:06
> À: Picard, Cyril; pgsql-sql(at)postgresql(dot)org
> Objet: Re: [SQL] passing null parameter to plpgsq functions
>
> From: "Picard, Cyril" <cyril(dot)picard(at)eads-dsn(dot)com>
>
> > Hello
> > I wrote a plpgsql function with few parameters ; when I call the
> function,
> > some of the parameters can be null.
> > In this case, all the parameters are considered as null in the
> function's
> > body ! is it a feature ? how can I work around this ?
>
> It's a feature in versions before 7.1 (or possibly 7.0.x) you can still
> get
> that behaviour in 7.1 by asking for strict null handling on a specific
> function.
>
> The only remedy AFAIK is to upgrade.
>
> - Richard Huxton
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2001-04-03 11:51:57 | Re: passing null parameter to plpgsq functions |
Previous Message | Richard Huxton | 2001-04-03 08:05:32 | Re: passing null parameter to plpgsq functions |