ID: 6339
Updated by: [EMAIL PROTECTED]
Reported By: dpetrov at nchcapital dot com
-Status: Analyzed
+Status: Closed
Bug Type: Feature/Change Request
Operating System: FreeBSD 3.4
PHP Version: 4.0.2
New Comment:
This bug has been fixed long, long ago, closing it:)
Previous Comments:
------------------------------------------------------------------------
[2000-12-11 21:12:52] [EMAIL PROTECTED]
Actually, the same thing happens no matter what the database
is, so I'm going to reclassify this as a Feature Request, since there
is a work around, and the syntax being used here
doesn't really make a whole lot of sense.
The basic issue: If you do not store the result of the
*_pconnect(), PHP discards it.
------------------------------------------------------------------------
[2000-09-29 21:17:35] dpetrov at nchcapital dot com
This confirmed to be a problem in version 4.0.2 as well
------------------------------------------------------------------------
[2000-08-24 18:01:50] dpetrov at nchcapital dot com
I am giving the simplest example possible:
sybase_connect("abc","def","jkl"); // or die("Can't connect!");
$res=sybase_query("Select * FROM Companies");
I always get this:
Warning: 1 is not a valid Sybase-Link resource in ...
Yet, if I replace 1st line with this:
$somevariable = sybase_connect("abc","def","jkl"); // or die("Can't
connect!");
then everything works just fine (even though I do not really use
$somevariable anywhere).
This probably means that the link it not being registered properly
internally.
I did not have this problem with Sybase-dblib (yet there is a big
problem wirg sybase_fetch_row - it core dumps PHP/Apache).
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=6339&edit=1
