| From: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(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-12 11:16:10 |
| Message-ID: | AANLkTikWLBniH-QRKa0AL+O71+DnTyizn770Hd89d5Lu@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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(at)gmail(dot)com>
> 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 | Rémi Zara | 2011-02-12 12:34:42 | pika failing since the per-column collation patch |
| Previous Message | mac_man2008@yahoo.it | 2011-02-12 11:13:04 | Re: Sorting. When? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thor Michael Støre | 2011-02-13 18:03:29 | Re: UDT arrays |
| Previous Message | Robert Haas | 2011-02-11 02:56:16 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |