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 |
Properly fix
Bug: 10162Signed-off-by: Michael J Rubinsky <mrubinsk@horde.org>2 files changed, 9 insertions(+), 6 deletions(-)
http://git.horde.org/horde-git/-/commit/4d8de4cff05871b1e24d8bb756cbeba685629b0c
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.
trough the fix you've done.
Assigned to Michael Rubinsky
State ⇒ Feedback
to the list though. Does this fix things for you?
Bug: 10162one more config param to remove from the dsn1 files changed, 2 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/905205f6e274b6934057c6764baa17050334aa80
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
New Attachment: 0001-Don-t-pass-non-valid-params-to-factory-db-when-using.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Setting a custom DB for Kronolith is generating errors
Type ⇒ Bug
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.