[dev] Support for multiple DB's (a/k/a application specific DB configuration)

[Michael M Slusarz]

Looking for input on an easy way to support multiple DB's.

Example: the new IMAP caching DB code.  Storing cached IMAP data in a  
structured database makes sense because we are querying via things  
like metadata type and/or Message UID.  This is better done via a  
database query rather than the hackish workaround of storing data  
within "slices" using Horde_Cache.

On the flip side, we don't need to persistence and/or reliability of a  
full database system.  So storing this data in the same DB as things  
like Horde preferences doesn't make a lot of sense either.

It would be nice to allow an admin to do something like, say, create a  
local sqlite database solely for the purposes of caching IMAP data.   
However, I'd rather keep things like database object creation out of  
configuration files (i.e. imp/config/backends.local.php).   
Additionally, there really is no way to populate this new database  
with the schema, since our database scripts are hardwired to the Horde  
DB configuration.

So thoughts on a coherent way of supporting this would be great.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]