I've been working on adding the functionality into the jdbc driver and
I'm having some issues.
Currently the bind message does not know anything about directionality
of the parameter. This means that considerable gyrations need to be done
by the driver to transform
create function foo( out p1 int, in p2 int, out p3 int) ....
then a subsequent
"{call = select foo(?,?,?)}
This would need to be currently transformed into select foo(?), with the
other two being discarded.
It seems to me that the bind message needs to support the notion of
direction in order for this to work cleanly.
Alternatively we could punt and use SQL Server's mechanism where they
only support IN, and INOUT, which would require all parameters to be
sent to the procedure.
On a related note, drop function needs to support the in/out direction.
Dave
--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
