| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OUT parameters in PL/Java |
| Date: | 2005-04-13 14:01:41 |
| Message-ID: | 6796.1113400901@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Hallgren <thhal(at)mailblocks(dot)com> writes:
> thhal=# create function javatest.recordExample(int, int) returns record
> as 'org.postgresql.pljava.example.ComplexReturn.complexReturn' immutable
> language java;
> CREATE FUNCTION
> thhal=# select * from javatest.recordExample(3, 4) as (foo int, bar int,
> baz timestamptz);
> ERROR: could not determine row description for function returning record
Hmm. I think this is not your bug. Is the call coming from
evaluate_function in clauses.c? We need to either prevent that from
pre-evaluating a function returning RECORD, or fix it so it can pass
the expected tuple descriptor ... probably the former :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2005-04-13 17:15:39 | Re: OUT parameters in PL/Java |
| Previous Message | Thomas Hallgren | 2005-04-13 06:39:51 | Re: OUT parameters in PL/Java |