FreeTDS Development Group

["Thompson, Bill D (London)" <ThompBil AT exchange.uk.ml.com>]

James,

> If you get dynamic queries working, I think we should coordinate with the
> others and issue a release.  Maybe when Nick is satisfied with error
> handling and Bill has compute rows working.  Brian already added (or has
the
> patch for, not sure) handling of stored procedure output parameters.  Not
to
> mention Nick's many fixes, including yesterday's to ct_cancel. 

It might be a good time to give you an update on this:

On the compute tokens I have completed the following :

Coded the wire protocols for the streams that support the "compute" results.
I've done this for TDS 5 and TDS 7/8. This has meant some not insubstantial
changes to the tdssocket structure.
I've got the results and row processing function is token.c to correctly
interpret and store the data resulting from a compute statement.

I've coded all the more "atomic" dblib functions that deal with compute
data. This covers about 10 previously unimplemented functions.
I've tested these, and created a dblib unit test for them too.

I've also worked on some of the higher level dblib functions like
dbnextrow() for example. 
This now covers the possibilities raised  by compute data and is now pretty
much to the manual specification.
There's also a few even higher level dblib functions which in turn call
dbnextrow(), for example dbprrow() and db