I really think we should have a way of telling if a array/row/record
variable is actually set to something, and I'm pretty sure that should be
unrelated to whether all the elements in it happen to be null.
+1. Also, can whatever syntax we introduce by something relatively
concise? Code that
On Sat, Oct 25, 2008 at 11:59 AM, Robert Haas [EMAIL PROTECTED] wrote:
I really think we should have a way of telling if a array/row/record
variable is actually set to something, and I'm pretty sure that should be
unrelated to whether all the elements in it happen to be null.
+1. Also,
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
I have a different issue I'm seeing, but I think it's related, and
ISTM it's a bug (on 8.2.10):
SELECT INTO v_prev *
FROM installments_static
WHERE id = (
Decibel! [EMAIL PROTECTED] writes:
Was anything ever done with
http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
http://archives.postgresql.org/pgsql-hackers/2008-09/msg01772.php
I have a different issue I'm
On Oct 24, 2008, at 7:19 PM, Tom Lane wrote:
Decibel! [EMAIL PROTECTED] writes:
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
Decibel! [EMAIL PROTECTED] writes:
... I would argue that rowvar_b IS NOT NULL should be false and rowvar_a
IS NOT NULL should be true.
While I don't necessarily disagree with you about what is sane, what
is required by the SQL spec seems pretty clear here.
regards,
