Re: procedure properties problem

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Rikard Pavelic" <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: procedure properties problem
Date: 2006-01-17 10:16:43
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40103D857@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of
> Rikard Pavelic
> Sent: 16 January 2006 15:02
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] procedure properties problem
>
> Hi!
> I don't know if this is missing feature or bug, but just to
> report this.
>
> If I create functions like
> create or replace function example(out data varchar) returns
> setof record as
> $$
> select data from table
> $$ language sql;
>
> pgAdmin displays it without 'returns setof record'.

The function written above will never work as you have a mismatch of
parameter and return types, but in answer to your query, the PostgreSQL
docs say:

"When there are OUT or INOUT parameters, the RETURNS clause may be
omitted."

(http://www.postgresql.org/docs/8.1/interactive/sql-createfunction.html)

If you remove the OUT/INOUT parameters, pgAdmin will display the
definition with the RETURNS SETOF clause.

Regards, Dave.

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2006-01-17 10:35:48 Re: pgagent jobs never start
Previous Message Dave Page 2006-01-16 15:14:48 Re: Bug Report - Find / Replace / Replace All