| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "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:36:35 |
| Message-ID: | 4846FCD3.5030108@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "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.
>
>
>
Right, and since the fill element is thus not optional it should be in a
fixed position in the argument list, ISTM, which can only mean it would
come first.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-04 20:37:18 | Re: Proposal: new function array_init |
| Previous Message | Pavel Stehule | 2008-06-04 20:34:01 | Re: Proposal: new function array_init |