From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Repair bug #2694 concerning an ARRAY[] construct whose inputs are |
Date: | 2006-11-06 18:21:47 |
Message-ID: | 20061106182147.B1F919FA666@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Repair bug #2694 concerning an ARRAY[] construct whose inputs are empty
sub-arrays. Per discussion, if all inputs are empty arrays then result
must be an empty array too, whereas a mix of empty and nonempty arrays
should (and already did) draw an error. In the back branches, the
construct was strict: any NULL input immediately yielded a NULL output;
so I left that behavior alone. HEAD was simply ignoring NULL sub-arrays,
which doesn't seem very sensible. For lack of a better idea it now
treats NULL sub-arrays the same as empty ones.
Tags:
----
REL8_0_STABLE
Modified Files:
--------------
pgsql/src/backend/executor:
execQual.c (r1.171.4.1 -> r1.171.4.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execQual.c.diff?r1=1.171.4.1&r2=1.171.4.2)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-06 18:21:58 | pgsql: Repair bug #2694 concerning an ARRAY[] construct whose inputs are |
Previous Message | Tom Lane | 2006-11-06 18:21:38 | pgsql: Repair bug #2694 concerning an ARRAY[] construct whose inputs are |