FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

Have a look at my dbsetopt()/gbclropt()/dbisopt() implementation for
DB-Library.

Currently, it only does the 4.2-compatible method for passing options to the
server.  It might be a good idea to start with a similar implementation for
ct_options().

Later, when tds_send_optioncmd() is finished, it could probably be used in
both places to implement the more efficient 5.0 options protocol.  (Also, it
might be a good idea to call it tds5_send_optioncmd().)

Cheers,
--nick

-----Original Message-----
From: freetds-admin AT lists.ibiblio.org
[mailto:freetds-admin AT lists.ibiblio.org]
Sent: Wednesday, February 12, 2003 1:33 AM
To: TDS Development Group
Subject: [freetds] ct_options


Owing to I know not what, some enchantment by the GNU fairy perhaps, and
beguiled into thinking it wouldn't be that hard, I wrote ct_options.  It
compiles and has been committed to CVS.  

Before you get too excited -- you know who you are -- it doesn't work yet.
 It checks all its inputs and is prepared to call a new function:
tds_send_optioncmd(), which is half-written.  I stopped where anyone
might, where I got stuck.  If you look at the function, you'll see what I
mean.  If you're someone familiar with reading and writing bytestreams
from/to the server, I could use a boost.  

I don't know how to go about reading from the server, having sent what I
need.  Also, I don't know what our "preferred" functions are.  What's the
highest level interface I can use?  

Also, I don't know if the options token exists in anything besides TDS 5. 
I'm assuming not.  

If someone who knows how could plunk a few comments in the code or rough
out for me what to do, I think I could have this working in a day or so.  

--jkl
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.