From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: strange evaluation Window function and SRF functions? |
Date: | 2012-07-30 17:12:15 |
Message-ID: | CAHyXU0yaDvb5j7fVHbMB9GfK1KBEnY4jnqnbTQt--+8k5TZy1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 30, 2012 at 11:47 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
> 2012/7/30 Thom Brown <thom(at)linux(dot)com>
>>
>> On 30 July 2012 17:19, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>>
>>> Hello
>>>
>>> I seen nice trick based on window function
>>> http://stackoverflow.com/questions/11700930/how-can-i-trim-a-text-array-in-postgresql
>>>
>>> but isn't it example of wrong evaluation? Result of row_number is not
>>> correct
>>
>>
>> Looks right to me. I guess the way to get the row_number they're after
>> out of the result set would involve changing OVER () to OVER (ORDER BY
>> unnest(myTextArrayColumn))
>>
>
> it looks like row_number is evaluated before SRF - this behave is absolutely
> undefined - for me - more native behave is different evaluation.
If it was me, I'd have expanded the array with generate_series (as
with the undocumented information_schema._pg_expandarray) and stacked
the array with array() not array_agg().
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2012-07-30 17:16:53 | Re: [PATCH] Support for foreign keys with arrays |
Previous Message | Alvaro Herrera | 2012-07-30 17:11:01 | Re: [PATCH] Support for foreign keys with arrays |