From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com>, dante(at)larkspark(dot)com, Postgres-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Returning RECORD from PGSQL without custom type? |
Date: | 2008-05-12 18:47:11 |
Message-ID: | 162867790805121147v76679d91x7039106815aec17a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2008/5/12 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "D. Dante Lorenso" <dante(at)lorenso(dot)com> writes:
>> I'd like to be able to do this:
>>
>> CREATE OR REPLACE FUNCTION "my_custom_func" (in_value bigint)
>> RETURNS SETOF (col1name BIGINT, col2name TEXT, ...) AS
>
> You realize of course that you can do this *today* if you use OUT
> parameters?
>
> CREATE OR REPLACE FUNCTION "my_custom_func" (in_value bigint,
> OUT col1name BIGINT, OUT col2name TEXT, ...)
> RETURNS SETOF RECORD AS
>
> The TABLE syntax is a bit more standards-compliant maybe, but it's not
> offering any actual new functionality.
it should minimalize columns and variables collision (for beginer
users).There isn't new functionality, but it can be more accessible
for new users. What I know, current syntax is for some people curios .
Regars
Pavel Stehule
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Justin | 2008-05-12 18:49:48 | Re: rounding problems |
Previous Message | Andy Anderson | 2008-05-12 18:18:57 | Re: rounding problems |