Hi Oliver
There are two problems.
>
> The first problem is a plpgsql problem in that particular function. It's
> broken regardless of how you call it. Here's how to fix it [...]
>
Thanks for insisting! I missed that fact. In the end, it looked like the
same error, but you're right about the plpgs
2011/2/17 Florian Pflug
> On Feb17, 2011, at 01:14 , Oliver Jowett wrote:
> > Any suggestions about how the JDBC driver can express the query to get
> > the behavior that it wants? Specifically, the driver wants to call a
> > particular function with N OUT or INOUT parameters (and maybe some othe
So what should I do? File a bug to the main Postgres mailing list? Or just
not support that feature?
2011/2/16 Oliver Jowett
> On 17/02/11 00:58, Robert Haas wrote:
> > On Wed, Feb 16, 2011 at 3:30 AM, Lukas Eder
> wrote:
> >> I'm not trying to fix the signature. I w
16, 2011 at 7:03 AM, Oliver Jowett
> wrote:
> > On 17/02/11 00:58, Robert Haas wrote:
> >> On Wed, Feb 16, 2011 at 3:30 AM, Lukas Eder
> wrote:
> >>> I'm not trying to fix the signature. I want exactly that signature. I
> want
> >>> to return 1 UD
That was my opinion, but you're saying that JDBC is not the cause either?
2011/2/16 Robert Haas
> On Wed, Feb 16, 2011 at 7:07 AM, Lukas Eder wrote:
> > So what should I do? File a bug to the main Postgres mailing list? Or
> just
> > not support that feature?
>
>
the database as a bug holder candidate.
Cheers
Lukas
2011/2/15 Robert Haas
> On Sat, Feb 12, 2011 at 6:16 AM, Lukas Eder wrote:
> > I had tried that before. That doesn't seem to change anything. JDBC still
> > expects 6 OUT parameters, instead of just 1...
>
> Oh, h
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
> On Tue, Jan 25, 2011 at 2:39 AM, Lukas Eder wrote:
> > So what you're suggesting is that the plpgsql code is causing the issues
>
> > Here, we've somehow got the first two fields of u_address_type - street
> and
> zip - squashed together into one column named 'street', and all the other
> > columns nulled out.
>
> I think this is the old problem of PL/pgsql having two forms of SELECT
> INTO. You can either say:
>
> SELEC