#32990 [Opn-Fbk]: Invalid statement handle
ID: 32990
Updated by: [EMAIL PROTECTED]
Reported By: kevin dot bluck at mail dot com
-Status: Open
+Status: Feedback
Bug Type: InterBase related
Operating System: Win2000
PHP Version: 5.0.5
New Comment:
First of all, I use Linux only. So I can't tell if it works on windows
or not. Second, I test only with firebird (which you propably know is
the follower of interbase..). I'm pretty sure my environment is too
different from yours to draw any conclusions whether this is fixed or
not. Thus you really need to test yourself. As soon as you can test,
reopen, otherwise let this rot.
Previous Comments:
[2005-09-12 17:50:31] kevin dot bluck at mail dot com
I'm sorry to say that in my development environment, I do not have the
ability to build CVS snapshots or install features like PDO that have
not yet been officially released, for reasons both technical and
political.
Inasmuch as I have provided a concise code snippet that reliably
reproduces the bug on my system, perhaps you could tell me if the bug
reproduces on *your* system, which presumably is already running the
bleeding edge.
[2005-09-10 23:31:05] [EMAIL PROTECTED]
And try using the PDO Firebird driver instead of ext/interbase..
[2005-09-10 23:29:11] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
[2005-09-10 01:23:59] kevin dot bluck at mail dot com
I just tested this against v.5.0.5 It still reproduces by the sample
code submitted 10 May 2005.
[2005-05-10 01:11:27] kevin dot bluck at mail dot com
It seems specifically to apply when a query is prepared with
ibase_prepare and run with ibase_execute; ibase_query does not show
warning.
This code reproduces on my system.
?php
function foo() {
$link = ibase_connect(Server:Database.gdb, SYSDBA,
masterkey);
$query = ibase_prepare( $link, SELECT * FROM Table );
ibase_execute( $query );
ibase_close ($link);
return -1; // generates the warning
}
$x = foo(); // warning displayed
?
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/32990
--
Edit this bug report at http://bugs.php.net/?id=32990edit=1
#32990 [Opn-Fbk]: Invalid statement handle
ID: 32990
Updated by: [EMAIL PROTECTED]
Reported By: kevin dot bluck at mail dot com
-Status: Open
+Status: Feedback
Bug Type: InterBase related
Operating System: Win2000
PHP Version: 5.0.5
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
Previous Comments:
[2005-09-10 01:23:59] kevin dot bluck at mail dot com
I just tested this against v.5.0.5 It still reproduces by the sample
code submitted 10 May 2005.
[2005-08-16 01:00:04] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2005-08-08 19:52:50] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
[2005-05-10 01:11:27] kevin dot bluck at mail dot com
It seems specifically to apply when a query is prepared with
ibase_prepare and run with ibase_execute; ibase_query does not show
warning.
This code reproduces on my system.
?php
function foo() {
$link = ibase_connect(Server:Database.gdb, SYSDBA,
masterkey);
$query = ibase_prepare( $link, SELECT * FROM Table );
ibase_execute( $query );
ibase_close ($link);
return -1; // generates the warning
}
$x = foo(); // warning displayed
?
[2005-05-09 19:29:00] kevin dot bluck at mail dot com
Description:
Appears to be a reversion of previously closed Bug #14039: symptoms
seem identical to that bug report.
http://bugs.php.net/bug.php?id=14039
Commenting out the ibase_close call eliminates the warning message.
--
Edit this bug report at http://bugs.php.net/?id=32990edit=1
#32990 [Opn-Fbk]: Invalid statement handle
ID: 32990
Updated by: [EMAIL PROTECTED]
Reported By: kevin dot bluck at mail dot com
-Status: Open
+Status: Feedback
Bug Type: InterBase related
Operating System: Win2000
PHP Version: 5.0.4
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
Previous Comments:
[2005-05-10 01:11:27] kevin dot bluck at mail dot com
It seems specifically to apply when a query is prepared with
ibase_prepare and run with ibase_execute; ibase_query does not show
warning.
This code reproduces on my system.
?php
function foo() {
$link = ibase_connect(Server:Database.gdb, SYSDBA,
masterkey);
$query = ibase_prepare( $link, SELECT * FROM Table );
ibase_execute( $query );
ibase_close ($link);
return -1; // generates the warning
}
$x = foo(); // warning displayed
?
[2005-05-09 19:29:00] kevin dot bluck at mail dot com
Description:
Appears to be a reversion of previously closed Bug #14039: symptoms
seem identical to that bug report.
http://bugs.php.net/bug.php?id=14039
Commenting out the ibase_close call eliminates the warning message.
--
Edit this bug report at http://bugs.php.net/?id=32990edit=1
#32990 [Opn-Fbk]: Invalid statement handle
ID: 32990 Updated by: [EMAIL PROTECTED] Reported By: kevin dot bluck at mail dot com -Status: Open +Status: Feedback Bug Type: InterBase related Operating System: Win2000 PHP Version: 5.0.4 New Comment: Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to Open. Thank you for your interest in PHP. Previous Comments: [2005-05-09 19:29:00] kevin dot bluck at mail dot com Description: Appears to be a reversion of previously closed Bug #14039: symptoms seem identical to that bug report. http://bugs.php.net/bug.php?id=14039 Commenting out the ibase_close call eliminates the warning message. -- Edit this bug report at http://bugs.php.net/?id=32990edit=1
