Re: passing null parameter to plpgsq functions

From: "Richard Huxton" <dev(at)archonet(dot)com>
To: "Picard, Cyril" <cyril(dot)picard(at)eads-dsn(dot)com>, <pgsql-sql(at)postgresql(dot)org>
Subject: Re: passing null parameter to plpgsq functions
Date: 2001-04-03 08:05:32
Message-ID: 00a701c0bc14$dc4bd920$1001a8c0@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Picard, Cyril 2001-04-03 09:39:30 RE: passing null parameter to plpgsq functions
Previous Message Richard Huxton 2001-04-03 08:03:02 Re: Appropriate indices to create for these queries