Skip to Content.
Sympa Menu

freetds - RE: [freetds] FreeTDS & PEAR's db.php library

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] FreeTDS & PEAR's db.php library
  • Date: Wed, 9 Apr 2003 10:50:57 -0400

> From: Shawn Greene [mailto:sgreene AT azorus.com]
> Sent: April 9, 2003 10:22 AM
>
> I have been using FreeTDS 0.60 to connect to the MSSQL
> database here for a
> long time, and it works great. I have mod_php4 (v 4.3.2)
> installed with
> SybaseDB support and this setup works great when using the
> mssql_* commands to access the database.
...
> #2 how does FreeTDS allow php to use the mssql commands when
> /usr/local/lib/php/mssql.so is not there for it to utilize?

I don't understand what you mean by "mssql commands", Shawn, or, if I do,
then FreeTDS isn't "allowing" anything, really. It's up to the runtime
linker to find the appropriate library and resolve the call.

> #3 (part of #2) is it using sybase?

More nouns, please.

I'm not familiar with PEAR, but if it relies on DBD::Sybase then I don't see
why it can't be made to work. There are some things DBD::Sybase supports
that FreeTDS hasn't implemented (yet), but that doesn't sound like what
you've bumped into.

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.





Archive powered by MHonArc 2.6.24.

Top of Page