Oliver,
OK, so if I understand this correctly, we allow the OUT parameter
result set if it is a callablestatement ?
I don't think we can actually return two resultsets ie one for the
out parameters, and yet another if the function returns a resultset.
I don't believe the
backend has this facility.
On 1-Jun-05, at 9:34 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>
>> cstmt = conn.prepareCall("{call
>> Numeric_Proc (?,?,?)}");
>> msg.setMsg("Register the output parameter");
>> cstmt.registerOutParameter
>> (1,java.sql.Types.NUMERIC,15);
>> cstmt.registerOutParameter
>> (2,java.sql.Types.NUMERIC,15);
>> cstmt.registerOutParameter
>> (3,java.sql.Types.NUMERIC,15);
>> msg.setMsg("execute the procedure");
>> cstmt.executeUpdate();
>>
>
> Ok, so that is exactly the case I was talking about, a procedure
> that doesn't return a value or resultset, but has OUT parameters.
> We should mask the resultset we get from the backend in this case
> as it's just an implementation detail of our OUT mechanism. (i.e.
> executeUpdate() does not complain, executeQuery() does complain, etc)
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>
>