6.0.0-beta1
7/9/25

[#7825] MDB2 SQL Queries broken on PgSQL since bug 6997 resolved
Summary MDB2 SQL Queries broken on PgSQL since bug 6997 resolved
Queue Horde Framework Packages
Queue Version FRAMEWORK_3
Type Bug
State Resolved
Priority 3. High
Owners chuck (at) horde (dot) org
Requester sberthelot (at) emisfr (dot) com
Created 01/05/2009 (6029 days ago)
Due
Updated 01/12/2009 (6022 days ago)
Assigned 01/12/2009 (6022 days ago)
Resolved 01/12/2009 (6022 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/12/2009 05:04:46 PM Chuck Hagenbuch Comment #6
State ⇒ Resolved
Reply to this comment
Should be all set with this patch, though you may not be able to use 
both Postgres and multiple different databases. The debug handler 
causes an actual disconnect with postgres, not just a re-select of the 
database name.
01/12/2009 02:07:37 AM Chuck Hagenbuch Comment #4
State ⇒ Assigned
Assigned to Chuck Hagenbuch
Reply to this comment
I'm not sure I can reproduce this bug, but I can reproduce something 
like it. I'll try and take another look tomorrow when I'm at my dev 
machine that has postgres set up on it.
01/06/2009 01:41:57 PM sberthelot (at) emisfr (dot) com Comment #3 Reply to this comment
Does it help if you change the MDB2 options to include
emulate_prepares => true ?
It doesn't change anything, tried in config.php and directly in 
sql.php (adding by hand to $params or $this->_params around line 737)
01/06/2009 05:38:05 AM Chuck Hagenbuch Comment #2
State ⇒ Feedback
Reply to this comment
Does it help if you change the MDB2 options to include 
emulate_prepares => true ?
01/05/2009 01:41:04 PM sberthelot (at) emisfr (dot) com Comment #1
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ MDB2 SQL Queries broken on PgSQL since bug 6997 resolved
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
On Horde Groupware Webmail 1.2.1 after upgrade from 1.1.2, adding or 
removing an event, trying to sync with SyncML or anything that 
modifies the DB in SQL result in such errors :



ERROR:  prepared statement 
"mdb2_statement_pgsql_bdcc910d55095456df42b7f14346ed0a" does not exist

STATEMENT:  DEALLOCATE PREPARE 
mdb2_statement_pgsql_bdcc910d55095456df42b7f14346ed0a

LOG:  unexpected EOF on client connection



It seems to be related to bug #6997 since modifying _selectDB function 
in Share/sql.php:710 to remove the call to 
"$db->connected_database_name = '' " makes it work again. I didn't 
understand why this function was added but it seems to break MDB2 
prepared statements on PgSQL ...

Saved Queries