freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "James K. Lowden" <jklowden AT freetds.org>
- To: "Frank M. Kromann" <frank AT kromann.info>, FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Long column names and PHP
- Date: Thu, 28 Sep 2006 22:37:58 -0400
Frank M. Kromann wrote:
> Just checked PHP5.2 sources and there is no references to the TDS
> version used.
>
> All it displays is:
>
> MSSQL Support => enabled
> Active Persistent Links => 0
> Active Links => 0
> Library version => FreeTDS
>
> I think it would be possible to show the default version, but as the
> version can be specified in freetds.conf (per connection) it does not
> make much sense to display it.
Thanks for looking into it Frank. Now it's a mystery what the OP meant by
"phpinfo() still reports 7.0".
FWIW, I think it would still be worthwhile for a PHP script to be able to
interrogate the connection to discover the TDS version currently in force.
Yes, one can set it in freetds.conf, but for a variety of reasons (wrong
directory, wrong dataserver section, etc.) it might not get used.
Regards,
--jkl
> > Thomas, Christopher (LLU) wrote:
> > > You are right that I was connecting using 4.2. I
> > > couldn't find the version from the TDSDUMP. But I checked the output
> > > from phpinfo() and it said 7.0, but I guess the freetds.conf file
> > > overrides whatever PHP has selected. After I changed the version
> inside
> > > freetds.conf to 8.0, everything worked perfectly. Funny thing is
> > > phpinfo() still reports 7.0.
> >
> > I don't know what PHP is doing. Using a current snapshot and assuming
> > you're using the mssql extension, you can see in the TDSDUMP log the
> order
> > of db-lib calls. And PHP could learn the TDS version only from the
> db-lib
> > function dbtds(). Anything else is just guesswork. (If you're using
> > ODBC, then I don't know.)
> >
> > We used to include the TDS version at the top of the log when
> connecting.
> > I noticed it got dropped some time ago. That was probably
> > inadvertent, because I don't remember any discussion and can't see any
> > advantage.
> I'll
> > look into putting it back.
> >
> > Glad you posted. If you were confused, someone else surely will be,
> too.
> >
> >
> > --jkl
> > _______________________________________________
> > FreeTDS mailing list
> > FreeTDS AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/freetds
> >
>
>
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
-
[freetds] Long column names and PHP,
Thomas, Christopher (LLU), 09/26/2006
- Re: [freetds] Long column names and PHP, James K. Lowden, 09/26/2006
- <Possible follow-up(s)>
-
Re: [freetds] Long column names and PHP,
Thomas, Christopher (LLU), 09/27/2006
- Re: [freetds] Long column names and PHP, James K. Lowden, 09/27/2006
-
Re: [freetds] Long column names and PHP,
Frank M. Kromann, 09/28/2006
- Re: [freetds] Long column names and PHP, James K. Lowden, 09/28/2006
- Re: [freetds] Long column names and PHP, Thomas, Christopher (LLU), 09/29/2006
- Re: [freetds] Long column names and PHP, Frank M. Kromann, 09/30/2006
- Re: [freetds] Long column names and PHP, Frank M. Kromann, 09/30/2006
Archive powered by MHonArc 2.6.24.