From: | George MacKerron <g(dot)j(dot)mackerron(at)lse(dot)ac(dot)uk> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Functions returning setof record -- can I use a table type as my return type hint? |
Date: | 2011-08-12 17:01:23 |
Message-ID: | 24C47454-4DE0-4793-8C63-24DA8A60F36B@lse.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12 Aug 2011, at 17:43, Merlin Moncure wrote:
> you can't have it both ways. at the time the function call is
> executed, the return type/fields must be known. you can do this by
> either a. explicitly defining the function return type or b.
> describing the function return type in the function call, or c. use a
> generic type to hold the output record structure which can be
> parsed/dealt with later, like text or hstore.
Thanks.
I'm trying to do your option (a) -- defining the function return type.
But I want to do this by referring to an existing table type -- which I know the returned fields must match -- rather than laboriously retype the field definition list for that table.
The problem is that I can't make the database accept the table type as a field definition list, when that seems like a perfectly sensible (and in this case much more convenient) way to define the fields that will be returned.
(With apologies for thoughtless top-posting in reply to Ray's earlier message).
Please access the attached hyperlink for an important electronic communications disclaimer: http://lse.ac.uk/emailDisclaimer
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2011-08-12 18:03:15 | Re: COPY from .csv File and Remove Duplicates |
Previous Message | Rob Sargent | 2011-08-12 16:44:14 | Re: Functions returning setof record -- can I use a table type as my return type hint? |