| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 22:02:00 |
| Message-ID: | 429CDED8.8010704@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches pgsql-sql |
Tom Lane wrote:
> 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?
>
I poked around a bit, and that was the best I could come up with. I'll
take another look.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2005-05-31 22:22:18 | Re: Deadlock with tsearch2 index ... |
| Previous Message | Tom Lane | 2005-05-31 21:58:03 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2005-06-01 09:21:47 | patch for between symmetric, asymmetric (from TODO) |
| Previous Message | Tom Lane | 2005-05-31 21:58:03 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PFC | 2005-05-31 23:11:45 | Re: Sum() rows |
| Previous Message | Tom Lane | 2005-05-31 21:58:03 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {} |