From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | "postgres hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: default values for function parameters |
Date: | 2008-11-24 09:40:31 |
Message-ID: | 162867790811240140s5360f97fi29c8b409dbed1c67@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/11/24 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> Pavel Stehule wrote:
>>
>> I have problem with sending patch, so I am send link
>> http://www.pgsql.cz/patches/defaults.diff.gz
>>
>> Example:
>> postgres=# create function fx(a int, b int default 30, c int default 40)
>
> Could you explain why you store the default expressions in a new posexpr
> type rather than in an array of text (compare pg_attrdef.adbin)?
>
>
I would to implement named params - and there expressions, that are
used as default params, should not be continual. I don't store params
as array of text because I would to eliminate repeated expression's
parsing. So I use similar machanism used for rules or views.
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2008-11-24 09:40:44 | Re: Minor race-condition problem during database startup |
Previous Message | Magnus Hagander | 2008-11-24 09:15:16 | pgsql: Add support for matching wildcard server certificates to the new |