Skip site navigation (1) Skip section navigation (2)

Re: Bug with callable statement and output parameters

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Bug with callable statement and output parameters
Date: 2006-05-11 02:24:58
Message-ID: 9726A637-9B48-426F-91A9-E1CBB6F1265B@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Kris,

Do you remember why we need outParmBeforeFunc. Did changes I made  
break this, or has this been broken for a while ?

Dave
On 10-May-06, at 8:52 PM, Kris Jurka wrote:

>
>
> On Thu, 4 May 2006, Dave Cramer wrote:
>
>> Kris,
>>
>> Ok, this should be it....
>
> This does not work for V2 protocol connections.  While we don't  
> support OUT/INOUT parameters over V2, we do support {? = call func()}.
>
> Kris Jurka
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>


In response to

Responses

pgsql-jdbc by date

Next:From: Patric BechtelDate: 2006-05-11 02:26:57
Subject: Re: Query length restriction in v3 protocol?
Previous:From: Kris JurkaDate: 2006-05-11 00:52:28
Subject: Re: Bug with callable statement and output parameters

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group