From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stuart Rison <rison@biochemistry.ucl.ac.uk>
Cc: pgsql-general <pgsql-general@postgresql.org>
Cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: [GENERAL][SQL] Getting multiple field unique index to distinguish NULLs.
Date: Fri, 10 Sep 1999 15:07:18 -0400
Message-ID: <10806.936990438@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.10.9909101626270.821-100000@bsmlx17>
Stuart Rison <rison@biochemistry.ucl.ac.uk> writes:
> Now this would work except that there's a problem with pl/pgSQL such that
> when you pass several values to a plpgsql function and one of them is
> NULL, then all values passed to the function become NULL.
Yes. That's not plpgsql's fault; there's a basic design limitation in
the function-call interface (only one isnull flag gets passed). There
has been some talk on the pghackers list of fixing this, but I do not
know if it will happen any time soon or not. Fixing that interface
would mean revising *all* the code that implements any SQL function or
operator, so it'd be pretty tedious --- and it'd break any C-coded
user functions, too. It'll probably get done eventually, maybe even
for 6.6, but don't hold your breath...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rison@biochemistry.ucl.ac.uk, pgsql-general@postgresql.org
Subject: Re: [GENERAL][SQL] Getting multiple field unique index to distinguish NULLs.
In-Reply-To: <10806.936990438@sss.pgh.pa.us>
References: <Pine.LNX.4.10.9909101626270.821-100000@bsmlx17> <10806.936990438@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox