php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #32990 Invalid statement handle
Submitted: 2005-05-09 19:29 UTC Modified: 2005-09-12 23:31 UTC
Votes:2
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:0 (0.0%)
From: kevin dot bluck at mail dot com Assigned:
Status: No Feedback Package: InterBase related
PHP Version: 5.0.5 OS: Win2000
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: kevin dot bluck at mail dot com
New email:
PHP Version: OS:

 

 [2005-05-09 19:29 UTC] 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-05-10 01:11 UTC] 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-09-10 01:23 UTC] 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-09-10 23:29 UTC] sniper@php.net 
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 23:31 UTC] sniper@php.net 
And try using the PDO Firebird driver instead of ext/interbase..
 [2005-09-12 17:50 UTC] 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-12 18:20 UTC] sniper@php.net 
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.
 [2005-09-12 18:44 UTC] kevin dot bluck at mail dot com 
Were you able to reproduce? Have any specific changes been made in response to this report? I can't tell from your replies.
 [2005-09-12 19:18 UTC] sniper@php.net 
No, I can't reproduce. If you're not going to test the snapshot, let's make this "no feedback" until that.
 [2005-09-12 20:19 UTC] kevin dot bluck at mail dot com 
Would 5.1.RC1 be sufficiently current code to test against?
 [2005-09-12 23:31 UTC] sniper@php.net 
No. Stop reopening this until you have some real feedback.
 [2007-08-08 12:16 UTC] valo1_i at hotmail dot com 
shumm mira
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Wed May 14 02:01:27 2025 UTC