FreeTDS Development Group

["Rich Young" <rich AT experienceplus.com>]

After contacting the CentOS bug tracking folks for advice on what to do,
I upgraded to PHP-5.1.6 via the CentOSPlus repository, and the problem
doesn't happen in PHP5.

So I guess we can assign the bug to PHP 4.3.9, which is no longer
accepted for bug reports at PHP.net - upgrade to PHP 4.4.4 or PHP 5 if
it's showing up, and the fine folks of FreeTDS can cross it off of their
things to look into when everything else is finished and they're bored.

James and Freddy, thanks so much for helping me through this.  You guys
are great!

--Rich Young, IT Dept.
ExperiencePlus! Specialty Tours, Inc.
rich AT ExperiencePlus.com
1-800-685-4565  

> -----Original Message-----
> From: freetds-bounces AT lists.ibiblio.org 
> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of James 
> K. Lowden
> Sent: Wednesday, January 10, 2007 9:46 PM
> To: FreeTDS Development Group
> Subject: Re: [freetds] MS-SQL ntext fields?
> 
> Rich Young wrote:
> > is it possible that we're missing something more obvious
> > than all this?  I mean, if I have a query that works in 
> tsql and isql,
> > but fails when it's part of a PHP script, does that prove it's a PHP
> > bug?  
> 
> That it runs in tsql proves next to nothing, that FreeTDS is 
> internally
> consistent and can communicate with the server, which 
> nowadays we expect. 
> 
> 
> That it runs is isql proves something: isql is using FreeTDS 
> as the ODBC
> driver, and works correctly.  So, yes, you have one ODBC 
> client that is
> satisfied with FreeTDS's behavior.  That's to the good.  If I 
> were in your
> shoes, I'd take my query and my isql results (and my stand-alone PHP
> script failure) to the PHP folks and ask them what to do.  
> 
> The possibility remains that the problem lies on the boundary 
> of unixODBC
> and PHP, possibly tickled by something in FreeTDS.  It's impossible to
> know from here.  I hesitate to call it a bug without knowing what the
> documentation says and which program (if any) is not conforming to its
> documented behavior.  
> 
> But, yes, I'd say you've exhausted your search here.  From 
> what I see, the
> problem manifests itself in the upper layers, and it's 
> certainly PHP that
> segfaults.  Best would be if they can help you track down the wild
> pointer.  That would at least lead you in the right direction.  
> 
> HTH.  
> 
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>