From: | Ian Harding <iharding(at)tpchd(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Errors from Sub-select Not Showing Up |
Date: | 2003-07-30 09:31:58 |
Message-ID: | 3F27908E.1050807@tpchd.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Has anyone else seen cases where errors from subselects are not being
raised? I just had it happen again but can't find a simple case that
reproduces it. The query is like this:
insert into ...
select (a bunch of CASE statements specifying a subselect to use if the
value of the attribute is null)...
from...(a messy JOIN)
in which one of the CASE contains a subselect which has an "Attribute
not found" error when executed independently. However, the only way it
manifests itself is through a NOT NULL constraint not being satisfied in
the insert.
Should I spend any time trying to reproduce this in a simple case, or is
there some known stupid way of making this happen?
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2003-07-30 09:50:28 | Re: PostgreSQL consultant |
Previous Message | Kaare Rasmussen | 2003-07-30 09:28:49 | PostgreSQL consultant |