From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: polymorphic SQL functions has a problem with domains |
Date: | 2014-04-02 15:23:22 |
Message-ID: | CAFj8pRB8fmpomQqKHPjc1B2rKDubipFNDJBWT24GkqaWtNbJ-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2014-04-02 17:19 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > I was informed about impossibility to use a polymorphic functions
> together
> > with domain types
>
> > see
>
> > create domain xx as numeric(15);
>
> > create or replace function g(anyelement, anyelement)
> > returns anyelement as
> > $$ select $1 + $2 $$
> > language sql immutable;
>
> > postgres=# select g(1::xx, 2::xx);
> > ERROR: return type mismatch in function declared to return xx
> > DETAIL: Actual return type is numeric.
> > CONTEXT: SQL function "g" during inlining
>
> That example doesn't say you can't use polymorphic functions with domains.
> It says that this particular polymorphic function definition is wrong:
> it is not making sure its result is of the expected data type. I don't
> recall right now whether SQL functions will apply an implicit cast on the
> result for you, but even if they do, an upcast from numeric to some domain
> over numeric wouldn't be implicit.
>
But I am not able to enforce a casting in polymorphic function
or there is some possibility?
Regards
Pavel
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2014-04-02 15:47:53 | Re: polymorphic SQL functions has a problem with domains |
Previous Message | Tom Lane | 2014-04-02 15:19:12 | Re: polymorphic SQL functions has a problem with domains |