| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Markus Bertheau <twanger(at)bluetwanger(dot)de> |
| Subject: | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |
| Date: | 2005-05-31 21:58:03 |
| Message-ID: | 7686.1117576683@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches pgsql-sql |
Joe Conway <mail(at)joeconway(dot)com> writes:
>> + Oid element_type = planstate->ps_ResultTupleSlot->tts_tupleDescriptor->attrs[0]->atttypid;
Hmm, that makes me itch ... it seems like unwarranted familiarity with
the innards of the subplan; not only as to where it keeps things, but
when things have been initialized. Perhaps we have no choice, but isn't
the datatype available on the current plan level?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2005-05-31 22:02:00 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. |
| Previous Message | Joe Conway | 2005-05-31 21:31:16 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2005-05-31 22:02:00 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. |
| Previous Message | Joe Conway | 2005-05-31 21:31:16 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2005-05-31 22:02:00 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. |
| Previous Message | Joe Conway | 2005-05-31 21:31:16 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |