Tickets :: [#9594] MySQLi multiple database queries causes fatal error

6.0.0-alpha14

7/2/25

Summary	MySQLi multiple database queries causes fatal error
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	No Feedback
Priority	1. Low
Owners
Requester	iron_hat (at) hotmail (dot) com
Created	02/23/2011 (5243 days ago)
Due
Updated	04/18/2011 (5189 days ago)
Assigned	02/26/2011 (5240 days ago)
Resolved	04/18/2011 (5189 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/18/2011 11:31:30 AM	Jan Schneider	State ⇒ No Feedback

03/26/2011 11:12:51 AM	Jan Schneider	Comment #5	Reply to this comment
Ping?

03/01/2011 08:19:13 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
Okay. Still potentially valid against Horde_Db itself which should be generally usable, but I need a test case. Ideally a contribution to the unit tests that shows the problem, but at least code I can reproduce with.

03/01/2011 05:41:48 PM	iron_hat (at) hotmail (dot) com	Comment #3	Reply to this comment
After more testing, it appears this is only a problem after calling a stored procedure. Since the main Horde applications do not use stored procedures, perhaps this could be labeled not a bug. Any chance you can boil the failing example down a little? Or give a specific example using the current Hermes code that I can reproduce?

02/26/2011 04:28:10 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
Any chance you can boil the failing example down a little? Or give a specific example using the current Hermes code that I can reproduce?

02/23/2011 07:43:05 PM	iron_hat (at) hotmail (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ MySQLi multiple database queries causes fatal error Queue ⇒ Horde Framework Packages Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Multiple queries to a mysql database using the mysqli Horde_Db adapter gives fatal errors such as: QUERY FAILED: Commands out of sync; you can't run this command now the application code is the following: $data = $GLOBALS['injector']->getInstance('Application_Driver')->getTankHistorybyId($id,$start_time, $end_time); ((Code to process data results)) $name = $GLOBALS['injector']->getInstance('Application_Driver')->getTankNamefromId($id); The driver code is much like the current state of Hermes.