Re: Re: postgres C function returning SETOF record gives RECORD TYPE NOT REGISTERED

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "raajarshi (dot)" <raajarshi(at)sify(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Re: postgres C function returning SETOF record gives RECORD TYPE NOT REGISTERED
Date: 2009-06-04 23:12:39
Message-ID: 21421.1244157159@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

"raajarshi ." <raajarshi(at)sify(dot)com> writes:
> to add a little clarification to the problem description, the transformed
> query (one which is actually run) returns the same result as the submitted
> query so actually the caller knows the number and type of fields to expect
> but they can be different for different calls as any query can be specified
> as the argument of the function.So would I have to create a placeholder type
> for each run of the query or what ??

You might want to look at the way contrib/dblink does this.

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Larry Silvermintz 2009-06-05 02:32:30 Update Triggers accessing new values and intercepting.
Previous Message Bruce Hyatt 2009-06-04 23:00:31 Yum Update Errors