On Wed, Jul 21, 2010 at 02:38:17PM -0400, Merlin Moncure wrote: > On Wed, Jul 21, 2010 at 2:28 PM, Robert Haas <[email protected]> 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?
Because that's not what the function actually does. FWIW, I'm for (im|ex)plode, as join()/split(), which I'd otherwise like, would run into too many issues with JOIN. Cheers, David. -- David Fetter <[email protected]> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: [email protected] iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
