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

From Lukas Eder
Subject Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function
Date
Msg-id AANLkTikWLBniH-QRKa0AL+O71+DnTyizn770Hd89d5Lu@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-jdbc
I had tried that before. That doesn't seem to change anything. JDBC still expects 6 OUT parameters, instead of just 1...

2011/2/11 Robert Haas <robertmhaas@gmail.com>
On Tue, Jan 25, 2011 at 2:39 AM, Lukas Eder <lukas.eder@gmail.com> wrote:
> So what you're suggesting is that the plpgsql code is causing the issues?
> Are there any indications about how I could re-write this code? The
> important thing for me is to have the aforementioned signature of the
> plpgsql function with one UDT OUT parameter. Even if this is a bit awkward
> in general, in this case, I don't mind rewriting the plpgsql function
> content to create a workaround for this problem...

Possibly something like address := (SELECT ...) rather than SELECT ...
INTO address?

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

pgsql-jdbc by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function
Next
From: Thor Michael Støre
Date:
Subject: Re: UDT arrays