| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, rushabh(dot)lathia(at)enterprisedb(dot)com |
| Subject: | Re: Function with defval returns error |
| Date: | 2008-12-15 20:37:50 |
| Message-ID: | 200812152237.51872.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday 15 December 2008 15:43:00 Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Rushabh Lathia wrote:
> >> I think this should not return error as the input args here is
> >> timestamp... inputs?
> >
> > In theory yes, but it's currently not that smart.
>
> This is truly horrid. Was that patch *really* ready to commit?
> I noticed some comments added to polymorphism.sql that certainly
> look like there's still a lot of half-bakedness in it.
There is that one case where a call that could be allowed is overly-cautiously
rejected. That only happens if you have a mix of overloading and default
parameters. It's not really half-baked in the sense that it is not
digestible; it's just not the greatest cake yet. It's
improvement-compatible.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-12-15 20:41:10 | Re: SQL/MED compatible connection manager |
| Previous Message | Jonah H. Harris | 2008-12-15 20:30:19 | Re: SQL/MED compatible connection manager |