Re: Untyped result (setof / rowset) from Functions ? - Mailing list pgsql-general

From Modern Mexican
Subject Re: Untyped result (setof / rowset) from Functions ?
Date
Msg-id MPBBJNBFMGDOEMEFADNEOEOOBGAB.felipe@modernmexican.com
Whole thread Raw
In response to Re: Untyped result (setof / rowset) from Functions ?  (Richard Huxton <dev@archonet.com>)
Responses Re: Untyped result (setof / rowset) from Functions ?  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-general
thanks for the tip, but it would be nice if PG implemented it like MSSQL
(very simple and straight forward).

Felipe Sandoval


Modern Mexican wrote:
> Is there a technical reason why an untyped result (setof / rowset) from a
> function (sql or plpgsql) is not implemented ?
>
> Something Simple:
>
> CREATE FUNCTION foo(x int) RETURNS SETOF records AS
> 'SELECT t1.*, t2.* FROM t1 INNER JOIN t2 ON t1.a=t2a
> WHERE WHERE t1.id=$1'
> LANGUAGE SQL
>
> So I will not have to create a TYPE every time I return a SETOF JOINED
> tables or a sub-set of the columns of a table.

You can do this, but you have to specify what the type is when you call
it. There needs to be *some* type defined somewhere.

See the manuals - section 7.2.1.4 which gives the following example of
specifying what results you expect from a dblink() call.

SELECT *
     FROM dblink('dbname=mydb', 'select proname, prosrc from pg_proc')
       AS t1(proname name, prosrc text)
     WHERE proname LIKE 'bytea%';

--
   Richard Huxton
   Archonet Ltd



pgsql-general by date:

Previous
From: Lincoln Yeoh
Date:
Subject: Re: Securing Postgres
Next
From: "Stefan 'Kaishakunin' Schumacher"
Date:
Subject: Re: Securing Postgres