| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Decibel! <decibel(at)decibel(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: new function array_init |
| Date: | 2008-06-04 20:34:01 |
| Message-ID: | 162867790806041334l1a7ec350rd1e70f9e4349ff5a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2008/6/4 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2008/6/4 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>> Huh? That's completely nonsensical ... where will you determine the
>>> type of the array, if you don't have a sample element?
>
>> it is nonsens in current postgres. But null array is castable to anyarray no?
>
> If you mean an array of nulls, it still has to have an element type.
I know it - but there was discus about untyped array for empty arrays
like ARRAY[]
it is little bit similar
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-06-04 20:36:35 | Re: Proposal: new function array_init |
| Previous Message | Tom Lane | 2008-06-04 20:33:20 | Re: Change lock requirements for adding a trigger |