From: | rsmogura <rsmogura(at)softperience(dot)eu> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, <pgsql-jdbc(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
Date: | 2011-02-17 10:13:49 |
Message-ID: | 260f2c0a23d1bf495aa313f0d0ae36d5@mail.softperience.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Maybe change in backend to treat complex types marked in relation as
COMPLEX in same way as scalar values is solution, actually I don't know.
This can be determined by GUC variable so every one can be happy :)
On Thu, 17 Feb 2011 23:08:13 +1300, Oliver Jowett wrote:
> Lukas Eder wrote:
>
>> The result set meta data correctly state that there are 6 OUT
>> columns. But only the first 2 are actually fetched (because of a
>> nested UDT)...
>
> The data mangling was just a plpgsql syntactic issue, wasn't it?
>
> Oliver
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-02-17 10:15:07 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
Previous Message | Oliver Jowett | 2011-02-17 10:08:13 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-02-17 10:15:07 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
Previous Message | Oliver Jowett | 2011-02-17 10:08:13 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |