| From: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
|---|---|
| To: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Feature proposal and discussion: full-fledged column/function equivalence |
| Date: | 2014-08-01 16:33:07 |
| Message-ID: | 53DBC143.6080307@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/01/2014 06:28 PM, Vik Fearing wrote:
>> So with all this in mind, is there any reason why we can't or shouldn't
>> > allow:
>> >
>> > CREATE testfunction(test) returns int language sql as $$ select 1; $$;
>> > SELECT testfunction FROM test;
>> >
>> > That would allow first-class calculated columns.
>> >
>> > I assume the work is mostly at the parser/grammatical level. Is there
>> > any reason why supporting that would be a bad idea?
> This is already supported since forever.
>
> SELECT test.testfunction FROM test;
>
> This link might be of interest to you:
> http://momjian.us/main/blogs/pgblog/2013.html#April_10_2013
Sorry, that's not the link I wanted. This one is:
http://momjian.us/main/blogs/pgblog/2013.html#April_1_2013
Despite being posted on April 1st, it is not a joke. :)
--
Vik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-08-01 16:38:40 | Re: Very Limited Toast Compression on JSONB (9.4 beta 2) |
| Previous Message | Vik Fearing | 2014-08-01 16:28:57 | Re: Feature proposal and discussion: full-fledged column/function equivalence |