Fri, 10 Apr 2026 20:05:43 +0000 https://bugs.horde.org/ticket/9430 Share doesn't log Db errors Maybe the Horde_Db object injected into Horde_Share doesn't have a logger attached, but I just got an SQL error from Kronolith's shares that hasn't been logged to the Horde log. Mon, 06 Dec 2010 10:58:46 +0000 https://bugs.horde.org/ticket/9430#t61000 The db adapter injected into shares is obtained from the injector, so this would affect any Horde_Db using code (if its due to no attached logger). What were you doing when you got the error, and do you know what the error was? Mon, 06 Dec 2010 14:04:33 +0000 https://bugs.horde.org/ticket/9430#t61001 This was a duplicate key error when creating a new calendar, because I didn't run the migration scripts yet. Mon, 06 Dec 2010 16:12:10 +0000 https://bugs.horde.org/ticket/9430#t61004 Changes have been made in Git for this ticket: Exceptions should be logged at error level, not debug. Bug: 9430 http://git.horde.org/horde-git/-/commit/864d3e31153b28c99b9a21962ddfff18a54375d0 Tue, 07 Dec 2010 15:13:12 +0000 https://bugs.horde.org/ticket/9430#t61020 Changes have been made in Git for this ticket: Clean up exceptions and logging. Inject Horde_Log_Logger, don't log exceptions from Horde_Db_Adapter when running queries, since those would be logged by the adapter, don't log queries in client code, it's logged by the adapter. Partially relates to Bug: 9430 http://git.horde.org/horde-git/-/commit/14800f5a422cf05a2a1e01394488273b5da7232f Tue, 07 Dec 2010 15:13:25 +0000 https://bugs.horde.org/ticket/9430#t61021