Re: Re: regexp_matches illegally restricts rows -- just a documentation issue?
От | Robert Haas |
---|---|
Тема | Re: Re: regexp_matches illegally restricts rows -- just a documentation issue? |
Дата | |
Msg-id | q2i603c8f071004060910ta4ea434eiefb338ed6f18f519@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: regexp_matches illegally restricts rows -- just a documentation issue? (Josh Berkus <josh@postgresql.org>) |
Ответы |
Re: Re: regexp_matches illegally restricts rows -- just a
documentation issue?
|
Список | pgsql-bugs |
On Tue, Apr 6, 2010 at 1:06 AM, Josh Berkus <josh@postgresql.org> wrote: > On 4/5/10 9:16 PM, Josh Berkus wrote: > >> I can't see how this is anything but a bug; as far as I know, nothing in >> the target list is allowed to restrict the number of rows which are >> returned by the query. =A0We should get 7 rows, 3 of which have an empty >> array or a NULL in the 2nd column. > > Just noticed it's a SETOF[] function. =A0Which makes it odd that I can > call it in the target list at all, but explains the row restriction. > > It's still confusing behavior (three regulars on IRC thought it was a > bug too) and users should be warned in the documentation. =A0Not sure > exactly where, though ... maybe in 9.7? While I understand why this is confusing, it's really very normal behavior for a SRF, and I don't really think it makes sense to document that this SRF behaves just like other SRFs... ...Robert
В списке pgsql-bugs по дате отправления: