Re: Another issue in default-values patch: defaults expanded too soon

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Another issue in default-values patch: defaults expanded too soon
Date: 2008-12-16 23:53:17
Message-ID: 17701.1229471597@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> We could say that changing the type of a default argument for a polymorphic
> argument isn't allowed just like changing the return value.

The point I was trying to make is that allowing defaults for polymorphic
args at all is going to cause a very significant amount of work and
complication, of which enforcing the above check is just a small part.
I wanted to see a plausible use-case for it before expending that work.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-12-17 00:07:35 Variadic parameters vs parameter defaults
Previous Message Gregory Stark 2008-12-16 23:45:35 Re: Another issue in default-values patch: defaults expanded too soon