| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "Grzegorz Jaskiewicz" <gj(at)pointblue(dot)com(dot)pl>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Subject: | Re: WIP: default values for function parameters |
| Date: | 2008-12-09 14:35:21 |
| Message-ID: | 14319.1228833321@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> select foo(777, three=> '{1,2,3,4,5});
> it's more safe and more readable.
... and it breaks an operator that's already in use.
> I did some test, and I thing so it is implementable. I had to solve
> problem with hstore module. There is defined operator => too, what is
> bad. But we can implemented in transformation and it should by
> disabled via GUC, so it's solveable.
What's wrong with the "expr AS parameter_name" syntax that we've
discussed before? (And no, having a GUC that changes the meaning
of "=>" isn't an acceptable workaround.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-12-09 14:36:35 | Re: new libpq SSL connection option |
| Previous Message | Andrew Chernow | 2008-12-09 14:34:54 | Re: new libpq SSL connection option |