From: Juris Zeltins <juris.zeltins@gmail.com>
To: John DeSoi <desoi@pgedit.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: pl/pgsql problem with return types
Date: Fri, 11 Mar 2005 14:50:13 +0200
Message-ID: <42319405.5050603@gmail.com> (raw)
In-Reply-To: <9ECE66EE-922B-11D9-B332-000A95B03262@pgedit.com>
References: <423178FC.3050107@gmail.com>
<9ECE66EE-922B-11D9-B332-000A95B03262@pgedit.com>
Yep.. i have solved this problem by specifying
the correct return type and variable type (should be the same)
but as said, in some cases pl_exec executes with type conversion.
as real example - i have :
return type = SETOF new type "category_node(catid, pcatid)"
variable = R, SR -> RECORD
and
FOR R IN select * from ...
LOOP
RETURN NEXT R; /* add RECORD to SETOF_of_CATEGORY_NODE */
....
and works...
the problem seems is teh same - on altered tables there is some porblem
with this :)
Actualy - return type & variable in "RETURN NEXT" must be the same type.
// Solved
John DeSoi wrote:
>
> On Mar 11, 2005, at 5:54 AM, Juris Zeltins wrote:
>
>> FOR P IN select pageid from pages
>>
>
> This way you are only getting the pageid column. I think what you want is
>
> FOR P in select * from pages
>
> so that P contains the complete pages record.
>
>
> John DeSoi, Ph.D.
> http://pgedit.com/
> Power Tools for PostgreSQL
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: juris.zeltins@gmail.com, desoi@pgedit.com
Subject: Re: pl/pgsql problem with return types
In-Reply-To: <42319405.5050603@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox