From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | Thangalin <thangalin(at)gmail(dot)com> |
Cc: | pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Bug: Reverting Return Type |
Date: | 2014-03-21 06:01:37 |
Message-ID: | CAG7mmoxxss=F4gvAJK9O-DE22fjHgqP=v=OEq4-g1STz_9S-jw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
What version of pgAdmin II are you using?
On Fri, Mar 21, 2014 at 11:29 AM, Thangalin <thangalin(at)gmail(dot)com> wrote:
> Hi,
>
> Create a new function that uses a TABLE return type definition:
>
> CREATE OR REPLACE FUNCTION testing(IN p_test bigint)
> RETURNS TABLE (id int) AS
> $BODY$
> SELECT 1 AS id
> $BODY$
> LANGUAGE sql STABLE;
>
> Expected Results
> The return type retains the ID column name and continues to use a
> TABLE for the result.
>
> Actual Results
> When viewed in pgAdmin3, it becomes:
>
> CREATE OR REPLACE FUNCTION testing(IN p_test bigint)
> RETURNS SETOF integer AS
> $BODY$
> SELECT 1 AS id
> $BODY$
> LANGUAGE sql STABLE
> COST 100
> ROWS 1000;
>
> The TABLE return type definition has been replaced.
>
> This has no immediate effect on the database, but any subsequent edits
> to the function through pgAdmin could catch developers unaware.
>
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support
>
--
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com>
*http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi>
From | Date | Subject | |
---|---|---|---|
Next Message | Thangalin | 2014-03-21 06:16:16 | Re: Bug: Reverting Return Type |
Previous Message | Thangalin | 2014-03-21 05:59:27 | Bug: Reverting Return Type |