FreeTDS Development Group

["Miguel Dias" <miguel_dias AT futurecom.pt>]

Hi,

I've been using freetds sucessfully on small php->mssql connections, but
right now I've got a weird behaviour with it.

the following example "sometimes" randomly caused the strangest thing

connectSQLServer(); //this function does login :)

$val1 = @mssql_result(mssql_query("SELECT field1 FROM table1 WHERE field1 =
'".trim($someval)."'"),0,0);

$val2 = @mssql_result(mssql_query("SELECT field1 FROM table1 WHERE field1 =
'".trim($someval)."' AND field2 LIKE 'XPTO%'"),0,0);


Now, we would assume that $val1 would have one value from the first select,
and $val2 would have one value from the second select. Strangely enough,
$val1 comes up empty and val $val2 ends up with the result from the first
select...

I haven't been able to reproduce this consistently, but it's happened twice
allready in 3/4 days. This is using freetds-5.1 (i've upgraded today to 5.2)
compilations are as follows:

freetds:
./configure  --prefix=/usr/local/freetds-5.2 --with-tdsver=4.2 --enable-msdb
lib

php (4.0.6)
./configure  --enable-track-vars --with-dbase --with-zlib --with-mysql --ena
ble-trans-sid --enable-xml --enable-inline-optimization --disable-debug --wi
th-pdflib --with-sybase=/usr/local/freetds-5.2/ --with-mssql --enable-mssql 
--enable-force-cgi-redirect --with-mysql=/usr --with-fastcgi --with-gd --wit
h-gnu-ld --enable-apc --enable-sysvshm

This is a redhat 6.0 linux, connecting to a mssql6.5 on an NT machine.


Regards,

Miguel Dias