Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
diego dupin complains :
"big problem of text protocol is it hasn't output parameter resultset (i've tryed to implement that myself but without success. i'm still too bad in c
goal is to send command CALL sp(1, 3) for example, and have all output parameters has a resultset, exactly like for binary protocol when capability SERVER_PS_OUT_PARAMS is set, without variables"
Is there a sound technical reason why this feature is tied to server-side prepared statements? I do not seem to find any.