FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: October 29, 2002 3:05 PM
> > 
> > If client-side cursors are ever implemented, I think it 
> would be to support
> > ODBC first.  Then if someone cared to, there might be 
> enough infrastructure
> > to bring them to the other APIs.  
> 
> why don't we implement it in libtds and then use?

I'm sure you would implement it in libtds and then use it.  I meant only
that the dblib and ctlib calls are somewhat different, so whatever you do
for ODBC cursors will probably need to be modified if/when it it's
generalized to support the other APIs.  ("It's not portable until it's
ported.")

> > I'd expect placeholders to appear in the 
> > next release of FreeTDS.  
> 
> Yes, although some lack of time... 

        :(

> > > Tests 20-22 test async calls (dbpoll() and friends). 
> Won't work with
> > > FreeTDS. No biggee.
> 
> I think this require work for full multi-threading... Sometime I think
> about the subject (not very difficult, just serialize and do 
> lock/checks on status change)

Threading is nice but not necessary.  These calls should be supported
without --enable-threadsafe.  It's just another form of nonblocking I/O.  

I don't know whether nonblocking is hard or easy, but I think the blocking
calls are a trivial case of the nonblocking ones.  To use dblib terms,
dbsqlexec() is really just dbsqlsend() plus dbsqlok(), and dbsqlok() is just
"while(!dbdataready()) sleep(1);".  More or less.  Properly indented, of
course.  

No equivalent in ODBC, is there?  

Regards, 

--jkl



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.