Re: Domains versus polymorphic functions, redux - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Domains versus polymorphic functions, redux
Date
Msg-id 88B40BE3-7E63-40A8-AA87-0564476ACC6B@kineticode.com
Whole thread Raw
In response to Domains versus polymorphic functions, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Domains versus polymorphic functions, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On May 24, 2011, at 9:12 AM, Tom Lane wrote:

> An alternative rule we could use in place of #2 is just "smash domains
> to base types always, when they're matched to ANYELEMENT".  That would
> be simpler and more in keeping with #1, but it might change the behavior
> in cases where the historical behavior is reasonable (unlike the cases
> discussed in my message referenced above...)  I find this simpler rule
> tempting from an implementor's standpoint, but am unsure if there'll be
> complaints.

I'm not sure where the historical behavior manifests, but this certainly seems like it might be the most consistent
implementation,as well. Which option is least likely to violate the principal of surprise? 

Best,

David



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Domains versus polymorphic functions, redux
Next
From: Greg Smith
Date:
Subject: Re: 9.2 schedule