| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeremy Drake <pgsql(at)jdrake(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, David Fetter <david(at)fetter(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com>, Mark Dilger <pgsql(at)markdilger(dot)com> |
| Subject: | Re: patch adding new regexp functions |
| Date: | 2007-02-18 23:27:11 |
| Message-ID: | 15229.1171841231@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Jeremy Drake <pgsql(at)jdrake(dot)com> writes:
> I will rename the functions regexp_split_to_(table|array) and I will add
> an optional limit parameter to the regexp_split_to_table function, for
> consistency and to avoid ordering concerns with LIMIT.
I'd go the other way: get rid of the limit option all 'round. It seems
like fairly useless complexity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Drake | 2007-02-18 23:56:08 | Re: patch adding new regexp functions |
| Previous Message | Tom Lane | 2007-02-18 23:19:49 | TopPlan, again |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Drake | 2007-02-18 23:56:08 | Re: patch adding new regexp functions |
| Previous Message | Jeremy Drake | 2007-02-18 23:10:51 | Re: patch adding new regexp functions |