freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>
- To: "Freetds (E-mail)" <freetds AT franklin.metalab.unc.edu>
- Subject: Dynamic, RPC and results
- Date: Wed, 20 Nov 2002 17:33:22 +0100
I don't understand where to store parameters returned from server.
Params can be stored in TDSSOCKET (param_info) and TDSDYNAMIC (res_info).
Some code (tds_process_dyn_result) store information in TDSSOCKET (res_info)
or TDSDYNAMIC (res_info) while parameters are stored always in param_info.
TDS cannot return params and row at the same time...
What's the problem of storing all data to param_info?
IMHO complex API in this way is ODBC because a single connection can have
multiple active statement each with param and row bindings... This mean that
it should write parameters to client after executing prepared query (ODBC
can't call RPC without the use of SQLPrepare/SQLExecute).
Do you agree to remove res_info from TDSDYNAMIC and param_info from
TDSSOCKET and distingue the two from result or anyone has different ideas?
freddy77
=================================
"STRICTLY PERSONAL AND CONFIDENTIAL
This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."
=================================
-
Dynamic, RPC and results,
ZIGLIO Frediano, 11/20/2002
- <Possible follow-up(s)>
- RE: Dynamic, RPC and results, ZIGLIO Frediano, 11/20/2002
Archive powered by MHonArc 2.6.24.