[Tickets #7972] Re: SQL SSL support

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7972
------------------------------------------------------------------------------
  Ticket             | 7972
  Updated By         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | SQL SSL support
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
-State              | Resolved
+State              | Feedback
  Priority           | 1. Low
  Milestone          | 3.3.4
  Patch              |
  Owners             | Chuck Hagenbuch
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2009-02-14 00:15) wrote:

> Perhaps this is a topic for another bug, but the handling of split
> reads appears to be broken in all of these places - array_merge is
> called to merge the original parameters with the read-only DB ones.
> However, both the persistent connections option and this new SSL one
> check !empty, so in the case where an SSL connection is desired for
> the original database but not for the new one you will get incorrect
> behavior.

This would be a separate issue. But why? A false key in the new array  
should override a true key in the original one just fine.

> Also, the references to "$this->_params" inside the splitreads block
> should be just "$params".

That was from your patch - can you provide an updated one for just that issue?

> How do I go about getting this same change made to
> Imp/Turba/Kronolith/etc?  Pretty much every application also needs it.

Patches would be great, or at least tickets to remind us.

Thanks!