Re: Schema version management

From: Joel Jacobson <joel(at)trustly(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Reykja <vikreykja(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schema version management
Date: 2012-07-05 15:20:44
Message-ID: CAASwCXccGzTxjKZFDc2M_Khhj7N+E2zUvPjAzTpfG-d4-ye55A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 5, 2012 at 5:17 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com>wrote:

> Agreed.
>
> However I am also against what seems to be the flow. Normally, you
> don't write overloaded plpgsql functions such as "equal". Case in
> point, the equality functions in core have funny names like "int4eq" and
> so on. Instead, at least in my experience, the overloaded functions
> people seem to have in their databases are like do_stuff_to_foobars()
> and you have one version for foos and another one for bars.
>
> If you're doing lots of equality functions, surely it would make more
> sense to package them up as an extension anyway along with all the other
> thingies you need for the type you're supposedly writing. So it's a
> completely different market than what we're aiming at here.

True, very true, I didn't think about that, you are right, I fully agree.
My vote is therefore on the "put all overloaded functions in the same file"
variant.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Glaesemann 2012-07-05 15:36:51 Re: Schema version management
Previous Message Alvaro Herrera 2012-07-05 15:17:35 Re: Schema version management