ID: 16583
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Apache2 related
Operating System: PLD Linux
PHP Version: 4.2.0RC4
New Comment:
Also not working. Ugly workaround with thread_resources = NULL; work
ID: 15900
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: ODBC related
Operating System: Linux
PHP Version: 4.1.2
New Comment:
Also:
echo odbc_result($table,5);
works but
$tname=odbc_result($table,5);
ID: 15900
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: *General Issues
Operating System: Linux
PHP Version: 4.1.2
New Comment:
In second first example i've cut lines with my example database name,
user
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.1.2
PHP Bug Type: *General Issues
Bug description: arguments to functions or again ODBC bug.
This function:
function GetTID($kid)
{
$a=$kid;
$conn = odbc_pconnect("$database", "$username", "$password");
$que
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.1.2
PHP Bug Type: ODBC related
Bug description: obdc_close is not closing sockets
after end of script odbc_close or odbc_close_all is not closing
connections. That may cause DoS as many open sockets can suck out
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.1.2
PHP Bug Type: ODBC related
Bug description: pretty random replies while using odbc functions
I'm wondering why code like this one:
$conn = odbc_pconnect("$database", "$username", "$password");
$query = "s
ID: 15880
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: ODBC related
Operating System: linux
PHP Version: 4.1.1
New Comment:
while using freetds+unixODBC+PHP i've found out that it's a problem of
odbc_fe
