On Feb 19, 2013, at 6:11 AM, Petr Jelinek <pjmo...@pjmodos.net> wrote:
>> some of the points you raise are valid, but in my (minority) opinion >> overloading creates more problems than it solves. You're not going to >> convince me that get() is *ever* a good name for a function - you might as >> well call it thing() or foo() for all the useful information that name > conveys. > > Let me join the minority here, +1 Well, that's why I called them get_json() and get_text(). Basically, I don't mind that the function name says something about the return type. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
