Skip to Content.
Sympa Menu

freetds - Re: dbdead, PHP, and Apache

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: dbdead, PHP, and Apache
  • Date: Mon, 16 Sep 2002 21:24:51 -0400


We provide DBDEAD() as a macro. It's source compatible but not ABI
compatible with 0.53. Yes, we probably should have bumped the library
version. I'm sure our release engineering department will take care of that
for the next release :-)

--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Monday, September 16, 2002 8:36 PM
To: TDS Development Group
Subject: [freetds] Re: dbdead, PHP, and Apache

[...]

Whoops. Wasn't the stated plan to provide DBDEAD() as a
backwards-compatible alias to dbdead()? Removing symbols without bumping
the soname is a library no-no. If the DBDEAD() symbol is being dropped
altogether, I'd very much like to see a 0.61 release that fixes the
soname.

Steve Langasek
postmodern programmer


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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page