On Fri, 2003-01-10 at 09:03, Honza Pazdziora wrote: > On Fri, Jan 10, 2003 at 08:38:42AM -0800, Michael Peppler wrote: > > > > As most of you are aware a lot of people are using the FreeTDS libraries > > (http://www.freetds.org) along with DBD::Sybase to access MS-SQL servers > > from non MS hosts (unix, linux). > > > > However, due to FreeTDS not implementing all of the Sybase Client > > Library API, and to the fact that not all of the TDS protocol supported > > by MS-SQL has been decoded there are a number of things in DBD::Sybase > > that fail when used with FreeTDS. > > > > I have been thinking of forking DBD::Sybase and creating a dedicated > > DBD::FreeTDS driver that would be geared towards working specifically > > with FreeTDS. > > I might not quite get it. DBD::Sybase + FreeTDS libraries worked > out of box for a few things I did here. What do you recommend instead, > for working with MS SQL?
DBD::Sybase *will* work with FreeTDS (mostly), although recent versions of DBD::Sybase implement a lot of things that don't exist in the FreeTDS libs (yet), such as RPC calls for stored procedures, text/image updating via ct_send_data(), etc. > Is it that you want to dedicate more of your time to FreeTDS part > and not being bothered with the Sybase/MS SQL part? Can't you just > ignore the Sybase posts? Actually it's the other way around. I get a lot of email for problems that are inherent to the FreeTDS libs, not to DBD::Sybase. For example DBD::Sybase's "make test" fails in a *lot* of places when used with FreeTDS (although it is getting better). A DBD::FreeTDS module would avoid this, and failures in "make test" would at least indicate real problems. > I do not see into the technical differences and it might be that new > versions of MS SQL will not work with FreeTDS libraries at all. But > still, for me FreeTDS libraries and DBD::Sybase did a great job and > I'd like it to continue, if possible. It will - DBD::FreeTDS would not be a replacement from DBD::Sybase+FreeTDS, it would be an alternative. FreeTDS is still being improved of course, and gets closer in behavior to Sybase's OpenClient. But I don't want to have to modify DBD::Sybase too much to map to (possible) idiosyncracies in FreeTDS. And of course we still have the case where both Sybase and MS-SQL access is required from the same script, and the FreeTDS support isn't deemed sufficient. Michael -- Michael Peppler Data Migrations, Inc. [EMAIL PROTECTED] http://www.mbay.net/~mpeppler Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or long term contract positions - http://www.mbay.net/~mpeppler/resume.html
