| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: to_string, to_array functions |
| Date: | 2010-07-21 18:38:17 |
| Message-ID: | AANLkTim76TvFJF7WsCqe5GoSTFejMdiK3RRYYWHyjFsx@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 21, 2010 at 2:28 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Yeah, I'd like some more votes, too. Aside from what I suggested
> (array_join/array_split), I think my favorite is your #5.
-1 for me for any name that is of the form of:
type_operation();
we don't have bytea_encode, array_unnest(), date_to_char(), etc. the
non-internal ones that we do have (mostly array funcs), are improperly
named imo. this is sql, not c. suppose we want to extend string
serialization to row types?
why not serialize/unserialize?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2010-07-21 18:47:21 | Re: multibyte charater set in levenshtein function |
| Previous Message | Pavel Stehule | 2010-07-21 18:37:42 | Re: patch: to_string, to_array functions |