From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com> |
Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, rsmogura <rsmogura(at)softperience(dot)eu>, 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-11 02:56:16 |
Message-ID: | AANLkTi=Nf_eqY0Ao1W41rMc4vp-B6+8j+AENJ2x-qJ--@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Tue, Jan 25, 2011 at 2:39 AM, Lukas Eder <lukas(dot)eder(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-02-11 03:05:18 | Re: ALTER EXTENSION UPGRADE, v3 |
Previous Message | Greg Smith | 2011-02-11 02:27:30 | Re: [PERFORM] pgbench to the MAXINT |
From | Date | Subject | |
---|---|---|---|
Next Message | Lukas Eder | 2011-02-12 11:16:10 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
Previous Message | mmg | 2011-02-10 21:12:25 | Re: Store a file in a bytea |