Invalid db resources after rewrite

Since the recent DB rewrite including Horde_Core_Binder_Comm

Fri, 14 May 2010 17:57:20 +0000

The error message is misleading, because the real error is:

Fri, 14 May 2010 17:57:58 +0000

The error message is misleading, because the real error is: Warning: mysql_select_db(): 90 is not a valid MySQL-Link resource in /usr/local/apache/php/lib/php/DB/mysql.php on line 307

Changes have been made in Git for this ticket: Bug #9027: U

Fri, 14 May 2010 19:02:51 +0000

Changes have been made in Git for this ticket: Bug #9027: Use Horde_Db_Pear binder to get DB objects delete mode 100644 framework/Core/lib/Horde/Core/Binder/Common.php create mode 100644 framework/Core/lib/Horde/Core/Binder/DbPear.php create mode 100644 framework/Core/lib/Horde/Core/Factory/DbPear.php http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Alarm.php?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Cache.php?rt=horde-git&r1=40e6e5beecbd4b69b590afaecbde1adf662ea3dc&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Common.php?rt=horde-git&r1=ff69ab061e00228d254232bc0049828415bfebef&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/co.php/framework/Core/lib/Horde/Core/Binder/DbPear.php?rt=horde-git&r=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Lock.php?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Perms.php?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/SessionHandler.php?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Token.php?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/co.php/framework/Core/lib/Horde/Core/Factory/DbPear.php?rt=horde-git&r=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/lib/Horde/Registry.php?rt=horde-git&r1=fd6f247c888a218953c7c19fe6cfe0d15aa69540&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03 http://git.horde.org/diff.php/framework/Core/package.xml?rt=horde-git&r1=9aab052c54d35a272e7c2799042243990ef60fbb&r2=c185c64bc1d178d54ef2c22de3d7a806677f5b03

Any chance this fixes things?

Fri, 14 May 2010 19:03:17 +0000

Any chance this fixes things?

Unfortunately not.

Fri, 14 May 2010 21:48:38 +0000

Unfortunately not.

Changes have been made in Git for this ticket: Use Horde_Db

Tue, 18 May 2010 17:17:14 +0000

Changes have been made in Git for this ticket: Use Horde_Db Bug #9027: Possible fix to Horde_Alarm SQL issue http://git.horde.org/diff.php/framework/Alarm/lib/Horde/Alarm/Sql.php?rt=horde-git&r1=b4ba6ed538947767af0304941d7c9fc93caad90d&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Alarm/package.xml?rt=horde-git&r1=a348a83b40a5653c565640fce45976a7c8d41cac&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Cache/lib/Horde/Cache/Sql.php?rt=horde-git&r1=b4ba6ed538947767af0304941d7c9fc93caad90d&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Cache/package.xml?rt=horde-git&r1=40e6e5beecbd4b69b590afaecbde1adf662ea3dc&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Alarm.php?rt=horde-git&r1=c185c64bc1d178d54ef2c22de3d7a806677f5b03&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Cache.php?rt=horde-git&r1=c185c64bc1d178d54ef2c22de3d7a806677f5b03&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Lock.php?rt=horde-git&r1=c185c64bc1d178d54ef2c22de3d7a806677f5b03&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Perms.php?rt=horde-git&r1=c185c64bc1d178d54ef2c22de3d7a806677f5b03&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Core/lib/Horde/Core/Binder/Token.php?rt=horde-git&r1=c185c64bc1d178d54ef2c22de3d7a806677f5b03&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Db/lib/Horde/Db/Adapter/Base.php?rt=horde-git&r1=5d6be5721093385fbe36f81ab7b6053ad0a5a042&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Db/lib/Horde/Db/Adapter/Pdo/Oci.php?rt=horde-git&r1=1a310b2de34193b3f984e4506d87b32de412a65e&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Lock/lib/Horde/Lock/Sql.php?rt=horde-git&r1=b4ba6ed538947767af0304941d7c9fc93caad90d&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Lock/package.xml?rt=horde-git&r1=7994594b3db35ca7478d608131d8faa214900fb5&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Perms/lib/Horde/Perms/Permission/SqlObject.php?rt=horde-git&r1=6f08cdbb1653c8c573e823589f7d83652e8cc739&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Perms/lib/Horde/Perms/Sql.php?rt=horde-git&r1=b4ba6ed538947767af0304941d7c9fc93caad90d&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Token/lib/Horde/Token/Sql.php?rt=horde-git&r1=4e98bb8db00f25a81403f912c2ca515c85a3c598&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/framework/Token/package.xml?rt=horde-git&r1=69d631396c9c6560805bd0aadf8f775797a45f2d&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/imp/lib/Injector/Binder/Sentmail.php?rt=horde-git&r1=f92994a77d09b7d2badebcf5d55404a74820b7ca&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869 http://git.horde.org/diff.php/imp/lib/Sentmail/Sql.php?rt=horde-git&r1=8763512795317061d4cef961637aeb2df6bcd6f4&r2=c5a17f712a86e81377a1f81a28c3d2c38597d869

> Changes have been made in Git for this ticket: > > Use H

Tue, 18 May 2010 17:29:25 +0000

> Changes have been made in Git for this ticket: > > Use Horde_Db > Bug #9027: Possible fix to Horde_Alarm SQL issue Avoiding PEAR DB debugging by simply converting to Horde_Db. Maybe this will work?

There's progress, the error comes from a different place now

Wed, 19 May 2010 12:25:18 +0000

There's progress, the error comes from a different place now, and is no longer fatal :) I can create the calendars just fine now, but in the logs I see: 2010-05-19T14:22:52+02:00 ERR: HEADHORDE [kronolith] Failed checking prefs for jan: DB Error: no database selected [pid 30003 on line 191 of "/home/jan/horde-git/framework/Prefs/lib/Horde/Prefs/Sql.php"]

> There's progress, the error comes from a different place n

Thu, 20 May 2010 17:18:11 +0000

> There's progress, the error comes from a different place now, and is > no longer fatal :) > I can create the calendars just fine now, but in the logs I see: > > 2010-05-19T14:22:52+02:00 ERR: HEADHORDE [kronolith] Failed checking > prefs for jan: DB Error: no database selected [pid 30003 on line 191 > of "/home/jan/horde-git/framework/Prefs/lib/Horde/Prefs/Sql.php"] Prefs is still using PEAR DB. FWIW, I don't see any of these errors when using stuff that relies on the PEAR DB binder. I am using Postgres though, so this might solely be a Mysql issue.

Looks like this has been fixed along the way.

Tue, 15 Jun 2010 15:22:25 +0000

Looks like this has been fixed along the way.