| From: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
|---|---|
| To: | |
| Cc: | "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: select into composite type / return |
| Date: | 2021-03-17 17:42:34 |
| Message-ID: | 9eb42b06-9cfa-1e4b-e42b-6f64e99675a5@ringways.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On 17/03/2021 17:26, Tom Lane wrote:
> AFAICS these two functions will have exactly the same output behavior,
> ie returning a "breakdown" composite type. If they act differently
> for you, either you are calling them in different ways or you made
> a mistake somewhere. I can't help noticing that the RETURN in the
> second function is calling a six-argument function, which is not the
> one you showed first. Maybe that version of do_breakdown() returns
> something different?
>
> regards, tom lane
Hi Tom,
Thanks for the quick response. The missing argument was because I had
to use pseudo details to protect intellectual property and I miss-typed
the code.
You were correct. The problem was not with the functions, but with how
I was calling them.
Gary
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Stainburn | 2021-03-18 10:05:12 | Re: select into composite type / return |
| Previous Message | Tom Lane | 2021-03-17 17:26:50 | Re: select into composite type / return |