Skip to Content.
Sympa Menu

freetds - RE: [freetds] Issue with freetds 0.61.2 ok on prior version which was <0.60

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] Issue with freetds 0.61.2 ok on prior version which was <0.60
  • Date: Tue, 16 Sep 2003 10:16:49 -0400

> -----Original Message-----
> From: Steve Hanselman [mailto:SteveH AT brendata.co.uk]
> Sent: September 16, 2003 6:20 AM
>
> Do you want me to do anything to help on this, I'm ok with my
> mods, but happy to help out?

Yes, thanks, Steve, I do. My build box hasn't been delivered yet, which is
why I've been so quiet.

I want to focus on a ct-lib unit test, and verify that ct-lib is behaving
correctly when passed two successive queries. If it is, I hope you'll be
able to discover what's surprising PHP.

--jkl


> -----Original Message-----
> From: James K. Lowden [mailto:jklowden AT schemamania.org]
> Sent: 06 September 2003 18:14
>
> There are two likely suspects, to my mind: ct-lib and PHP.
> It's fairly
> simple to modify a ct-lib unit test to mimic your query and
> show (or fix
> such) that ct-lib responds correctly. That much I'm competent to look
> into.
>
> I remember vaguely that there was some problem with PHP in this
> neighborhood, and ISTR a patch posted for it. But I didn't
> understand the
> issue fully and it was a few months back, so I might just be blowing
> smoke.
>
> --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