Re: patch adding new regexp functions
От | Peter Eisentraut |
---|---|
Тема | Re: patch adding new regexp functions |
Дата | |
Msg-id | 200702161319.56700.peter_e@gmx.net обсуждение исходный текст |
Ответ на | Re: patch adding new regexp functions (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: patch adding new regexp functions
Re: patch adding new regexp functions |
Список | pgsql-patches |
Am Freitag, 16. Februar 2007 08:02 schrieb Jeremy Drake: > On Thu, 15 Feb 2007, Peter Eisentraut wrote: > > I have no strong opinion about how matches are returned. Seeing the > > definitional difficulties that you point out, it may be fine to return > > them unordered. But then all "matches" functions should do that. > > > > For the "split" functions, however, providing the order is clearly > > important. > > Does this version sufficiently address your concerns? I don't think anyone asked for the start position and length in the result of regexp_split(). The result should be an array of text. That is what Perl et al. do. As for the regexp_matches() function, it seems to me that it returns too much information at once. What is the use case for getting all of prematch, fullmatch, matches, and postmatch in one call? -- Peter Eisentraut http://developer.postgresql.org/~petere/
В списке pgsql-patches по дате отправления: