FreeTDS Development Group

[Ken Collins <ken AT metaskills.net>]

1) I think many people wrongly confuse --with-tdsver as it has to be done 
with this version I am using or it does not work. They fail to realize this 
is only a default configuration. I have witnessed the same mistake for 
--enable-msdblib and the sybase too. 

2) I say keep --with-tdsver, especially since it is critical for TinyTDS now. 
I just recently found out that our usage of dbsetlversion() via DBLIB is not 
working as I expected it. So when passing (5) which is equal to 7.1/8.0 it 
will never connect to the DB. So our library is encouraging users to compile 
FreeTDS with 7.1 which let's us pass all the tests from 2000 to Azure. FYI, 
when people use TinyTDS with 0.91 and the changes others allowed us to put 
in, conf files and/or env variables are moot.

 - Ken

P.S. If anyone has advice on why dbsetlversion() is not doing what I expect, 
I'd love to hear it. I was thinking it would set the version in the login 
structure and work exactly like setting the TDSVER environment variable or 
"tds version" in a external conf file.


> From recent discussions, it seems that the 'tdsver' configure option 
> provides more 
> confusion than benefit.
> 
> From my ignorance of its intended use, I offer this proposal.  Feel free to 
> argue against it.
> 
> Propose: Ignore the "tdsver" option, and mark it obsolete in the user guide 
> documentation.
> 
>   Change 'configure' to ignore --tdsver if supplied. If one is offered, 
> print:
>       The --tdsver option is obsolete and will be ignored.
> 
>   Internally, the source will default to use the greatest TDS version that 
> the source 
> code supports.
> 
> Benefits:
>    1. simpler configuration
>    2. no other change in how ".conf" or ".ini" files shape the TDS version 
> that is 
> ultimately used.
> 
> -Mike Slifcak
> _____________