Re: Fwd: [JDBC] Weird issues when reading UDT from stored function - Mailing list pgsql-hackers

From Lukas Eder
Subject Re: Fwd: [JDBC] Weird issues when reading UDT from stored function
Date
Msg-id AANLkTikNjPoca5n7CusTEL2GoXNQuZeeF0vyegpsz3UF@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: [JDBC] Weird issues when reading UDT from stored function  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Fwd: [JDBC] Weird issues when reading UDT from stored function  (Robert Haas <robertmhaas@gmail.com>)
Re: Fwd: [JDBC] Weird issues when reading UDT from stored function  (rsmogura <rsmogura@softperience.eu>)
List pgsql-hackers
I'm not trying to fix the signature. I want exactly that signature. I want to return 1 UDT as an OUT parameter from a function.

Somewhere between JDBC and the database, this signature is lost, and JDBC's internal code tells me that I have to bind 6 OUT parameters, instead of 1. It happens to be so, because the UDT contains 6 attributes, so somehow the JDBC/database protocol flattens the UDT, and I think that's a bug, either in JDBC or in the protocol or in the database. My findings were that I can correctly read the UDT OUT parameter using the pgAdmin III tool, so I excluded the database as a bug holder candidate.

Cheers
Lukas

2011/2/15 Robert Haas <robertmhaas@gmail.com>
On Sat, Feb 12, 2011 at 6:16 AM, Lukas Eder <lukas.eder@gmail.com> wrote:
> I had tried that before. That doesn't seem to change anything. JDBC still
> expects 6 OUT parameters, instead of just 1...

Oh, hrm.  I thought you were trying to fix the return value, rather
than the signature.

I am not sure how to fix the signature.  Can you just make it return RECORD?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Ralf Wildenhues
Date:
Subject: Re: [Mingw-users] mingw64
Next
From: Cédric Villemain
Date:
Subject: Re: why two dashes in extension load files