On Thu, 2002-08-08 at 11:32, [EMAIL PROTECTED] wrote:
> 
> 
> All, thanks for the replies.
> DBD-Sybase-0.94   eliminated   the  error   (DBD-Sybase-0.94_2   crashed
> horribly though).
> 
> I do still have a nagging problem that I can't seem to find the solution
> for perl scripts. Some debug msgs are being printed out:
> 
> Changed database context to 'master'.
> Changed language setting to us_english.
> Changed database context to 'db_name'.

This is a known problem. If you are on a bigendian box (Sun Sparc, for
example) then the error numbers as reported to DBD::Sybase by FreeTDS
are wrong, and the filters that I have to remove these messages fail.

I know that this has been fixed by FreeTDS in recent CVS versions.

Michael

> On Thu, 8 Aug 2002, Simon Oliver wrote:
> 
> > You would probably do better to use DBD::Sybase with the FreeTDS
> > libraries.  
> > 
> > The ODBC API hasn't been as keenly developed for FreeTDS.  Here's the
> > blurb from the FreeTDS FAQ:
> > 
> > DBD::Sybase is the recommended option, and yes it does work with MSSQL.
> > You will need to install the perl DBI module and the FreeTDS package,
> > particularly the CTLib portion. Set your SYBASE environment variable to
> > /usr/local/freetds and install DBD::Sybase. Don't worry too much if some
> > of the tests fail. Do worry if the module doesn't compile. Make sure you
> > have the most recent version of FreeTDS installed. You can check the
> > mailing list archives or ask the mailing list for help. 
> > 
> > DBD::FreeTDS does not depend on the FreeTDS libraries. It is minimally
> > functional but it is considered alpha software and is not being actively
> > developed. 
> > 
> > >From Michael Peppler ([EMAIL PROTECTED]): 
> > Sybperl is a thin wrapper around the Sybase C APIs. It's a lot more mature
> > than DBI/DBD::Sybase (I've been working on it for 9 years :-) and it's
> > maybe more natural to use for someone who already knows the Sybase APIs
> > (or MS's DBlibrary). It's a little more powerful/flexible than DBI, though
> > obviously less portable. It's still actively maintained and developed (by
> > yours truly) 
> > 
> > >From Brian:
> > DBD::ODBC is the newest option available. Its primary advantage is not
> > having to load another DBI driver if you already have DBI::ODBC load for
> > other systems. On the downside, it may be a little less robust than
> > DBD::Sybase. 
> > 
> > 
> 
> 
-- 
Michael Peppler / [EMAIL PROTECTED] / http://www.mbay.net/~mpeppler
[EMAIL PROTECTED] / ZetaTools, Inc / http://www.zetatools.com
ZetaTools: Call perl functions as Sybase stored procedures!

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to