Re: Troubles upgrading to freetds-0.82

 

> -----Original Message-----
> From: Mikhail Teterin [mailto:[email protected]] 
> Sent: giovedì 26 giugno 2008 14.24
> To: ZIGLIO, Frediano, VF-IT
> Cc: [email protected]; [email protected]; [email protected]
> Subject: Re: Troubles upgrading to freetds-0.82
> 
> On четвер 26 червень 2008, ZIGLIO, Frediano, VF-IT wrote:
> = >  2. Similarly, shared libraries, such as libtds.so.5 is no 
> = > longer installed,
> = >     hurting binary compatibility (ABI) and, no doubt, some 
> = > Makefiles somewhere.
> = 
> = yes, we removed entirely libTDS (headers and libraries) from
> = distribution. This to assure future ABI.
> 
> It seems, a greater bunch of things are broken now, than I originally 
> thought -- php-backends no longer build, for example, as well as 
> libgda3-freetds:
> 
> 	http://www.freshports.org/databases/libgda3-freetds
> 	http://www.freshports.org/databases/php5-sybase_ct
> 
> Oh, well...
> 

I don't understand these pages... are there some kind of automatic build system??

> = >  I notice, that BLK_VERSION_100 and _110 are still defined in 
> = > cspublic.h
> = >  (both as CS_VERSION_100), but that's it -- the API 
> = > compatibility with the
> = >  older version is now broken.
> = 
> = :( fixed in a post patch at freetds.sf.net. James is 
> planning to package
> = an updated source package.
> 
> So, will there be a 0.83 sime time soon?
> 

no, a 0.82.1 probably

> In addition, my personal pet-peeve is the lack of /automatic/ 
> recognition of 
> Sybase vs. SQL-server. I'm sure there is a way -- at the low 
> level -- to 
> detect, what "flavor" the server is and set the 
> settings->msdblib flag 
> automatically regardless of the compile-time setting.
> 

Mmmm... yes, try to use version 4.2 to detect protocol version, however every time you'll have 2 connections instead of one, a good optimization would be to cache protocol version somewhere, let's say ~/.freetds.cache or similar... this would help for instance port too.

> Because, for example, currently one can only have either 
> databases/freetds or 
> databases/freetds-msdblib
> 
> 	http://www.freshports.org/databases/freetds
> or
> 	http://www.freshports.org/databases/freetds-msdblib
> 
> And the same application (or a toolkit like Sybtcl) can not 
> talk to both types 
> of servers /at once/, unless it is hacked to change a connection's 
> settings->msdblib itself, which means, it has to be 
> FreeTDS-aware, rather 
> than simply use the vendor's API.
> 

Mmm.... I think you are confusing server with client needs... msdblib means that client wants some msdblib thing, not that you are connecting to mssql...

freddy77

_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds