I'm not sure I can propose a scheme that would
work in all situations, but one could simply
considered the built-in data type underlying
the domain. In my case, this would mean deciding
between character varying and bytea, which seems to
work just fine.
As far as surprising behavior, isn't the s
"TJ O'Donnell" <[EMAIL PROTECTED]> writes:
> I really want two polymorphic functions, one taking
> a domain data type using varchar and one bytea.
These aren't polymorphic functions, actually; they're just overloaded.
> In that case, postgres complains that it cannot decide
> which one to use whe
When I define two polymorpic functions, one taking
varchar and one bytea, there seems to be no confusion
choosing the varchar version when called with
the untyped literal 'abc'.
I really want two polymorphic functions, one taking
a domain data type using varchar and one bytea.
In that case, postg
