| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Weird issues when reading UDT from stored function |
| Date: | 2011-01-11 01:13:47 |
| Message-ID: | 4D2BAECB.7040108@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On 11/01/11 13:24, Oliver Jowett wrote:
> On 11/01/11 12:06, Lukas Eder wrote:
>> ====================================
>> Output:
>> # of columns: 6
>> ("(""Parliament Hill"",77)",NW31A9)
>>
>> Why are there 6 columns? And why is the UDT incorrectly fetched (many
>> fields are missing)
>
> Looks to me like you're getting each field of the UDT as a separate
> column. You printed only the first column i.e. the 'street' part.
Oops, looking closer I see what you mean, that's actually 2 columns of
the surrounding type - street + zip? What are the values of the other 5
columns reported by the driver?
A loglevel=2 trace would still be useful here.
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-01-11 01:16:04 | Re: Compatibility GUC for serializable |
| Previous Message | Tom Lane | 2011-01-11 01:09:19 | Re: GIN indexscans versus equality selectivity estimation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Eder | 2011-01-11 15:55:52 | Fwd: Weird issues when reading UDT from stored function |
| Previous Message | Oliver Jowett | 2011-01-11 00:24:16 | Re: Weird issues when reading UDT from stored function |