From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Richards <miker@scifair.acadiau.ca>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Array Madness
Date: Tue, 14 Sep 1999 11:02:13 -0400
Message-ID: <16388.937321333@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.10.9909132250160.63880-100000@scifair.acadiau.ca>
Michael Richards <miker@scifair.acadiau.ca> writes:
> It seems that you can't have a NULL value in an array.
Seems like a reasonable idea. Go for it...
> Running an update and setting a single array value to null seems
> to nuke the entire array.
Yeah, it does, see ExecEvalArrayRef() in execQual.c: if the refassgnexpr
yields a null, it just drops out with a null result for the whole expr.
This could be fixed if the array routines had a representation for a
null element in an array, but they don't.
In the meantime, perhaps it would be better for ExecEvalArrayRef() to
raise an error if the assign source is null, rather than dropping the
whole contents of the array. Comments?
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, miker@scifair.acadiau.ca
Subject: Re: [SQL] Array Madness
In-Reply-To: <16388.937321333@sss.pgh.pa.us>
References: <Pine.BSF.4.10.9909132250160.63880-100000@scifair.acadiau.ca> <16388.937321333@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