Re: PROPOSAL FE/BE extension to handle IN/OUT parameters

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PROPOSAL FE/BE extension to handle IN/OUT parameters
Date: 2005-06-21 21:14:44
Message-ID: 17406.1119388484@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> The current situation with IN/OUT parameters requires that
> considerable juggling is required on the client end to not pass the
> OUT parameters in the query. This could be alleviated by adding two
> messages for stored procedure calls
> 1) PrepareCall which sent the types, and direction of the parameters
> 2) BindCall which sends the binds the parameters to the above

> Is it possible to get this into 8.1, or is this a total non-starter

Changing the protocol is a nonstarter at this late date in the release
cycle. I previously offered you a hack that would accomplish the same
thing (or at least it looks like the same thing to me): ignore
parameters of type VOID when looking up a function. Is that unusable
from your end?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-06-21 21:16:39 Re: Why is checkpoint so costly?
Previous Message Magnus Hagander 2005-06-21 20:34:48 Removing Kerberos 4