6.0.0-beta1
7/9/25

[#10162] Setting a custom DB for Kronolith is generating errors
Summary Setting a custom DB for Kronolith is generating errors
Queue Kronolith
Queue Version Git master
Type Bug
State Resolved
Priority 2. Medium
Owners mrubinsk (at) horde (dot) org
Requester goncalo.queiros (at) portugalmail (dot) net
Created 05/31/2011 (5153 days ago)
Due
Updated 06/02/2011 (5151 days ago)
Assigned 06/01/2011 (5152 days ago)
Resolved 06/02/2011 (5151 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
06/02/2011 02:18:16 PM Michael Rubinsky State ⇒ Resolved
 
06/02/2011 02:17:57 PM Git Commit Comment #6 Reply to this comment
Changes have been made in Git for this ticket:

Properly fix Bug: 10162 Signed-off-by: Michael J Rubinsky <mrubinsk@horde.org>

  2 files changed, 9 insertions(+), 6 deletions(-)
http://git.horde.org/horde-git/-/commit/4d8de4cff05871b1e24d8bb756cbeba685629b0c
06/02/2011 02:11:26 PM Michael Rubinsky Comment #5 Reply to this comment
Good point  :)

That, plus the fact that keeping it in Core would mean applications 
would require newer versions of Horde_Core to pick up the change 
(still debatable as to whether or not this is a BC break), it's 
probably cleaner to put this in Kronolith, as you originally suggested.


06/02/2011 10:50:24 AM goncalo (dot) queiros (at) portugalmail (dot) net Comment #4 Reply to this comment
No it doens't work because $type is an array, so it never passes 
trough the fix you've done.
06/01/2011 07:30:47 PM Michael Rubinsky Comment #3
Assigned to Michael Rubinsky
State ⇒ Feedback
Reply to this comment
Most of these are already removed in the Horde_Db factory. I added utc 
to the list though. Does this fix things for you?
06/01/2011 07:29:45 PM Git Commit Comment #2 Reply to this comment
Changes have been made in Git for this ticket:

Bug: 10162 one more config param to remove from the dsn

  1 files changed, 2 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/905205f6e274b6934057c6764baa17050334aa80
05/31/2011 02:22:23 PM goncalo (dot) queiros (at) portugalmail (dot) net Comment #1
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
New Attachment: 0001-Don-t-pass-non-valid-params-to-factory-db-when-using.patch Download
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Setting a custom DB for Kronolith is generating errors
Type ⇒ Bug
Reply to this comment
Using the admin interface to generate Kronolith conf (with a custom 
DB) is creating an invalid conf, because invalid things like 'table' 
and 'utc' will be passed has parameters to establish a new connection.
I attached a patch that fixes this, although i don't know if it 
wouldn't be better to fix the conf generation.

Saved Queries