[horde] installing ansel 2.0.2

[Michael M Slusarz]

Quoting Andreas Schulze <sca at andreasschulze.de>:

> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Indeed, sqlite would probably be a pretty bad choice to run Horde  
>> on in general for anything more than a small testing setup.
> that should be mentioned in INSTALL

I'm going to disagree with this statement.

I've spent a good part of the last month developing the initial NoSQL  
(for now, just Mongo DB) drivers for various Horde subsystems because  
a full RDBMS for these subsystems is absolute overkill.  Actions like  
cache/lock storage are pretty close to being doable via a simple hash  
table lookup.  Other things like preferences doesn't require any  
advanced SQL statements to correctly implement.  The only practical  
difference between sqlite and a full RDBMS system in these instances  
is pretty much the network availability of the latter (obviously,  
there's some locking/concurrency issues if you have thousands of  
users, but even then it's probably not as bad as you think since  
sqlite is pretty blazingly fast, especially if locally accessing).

That being said, there are certain Horde subsystems/applications that  
DO leverage advanced SQL queries.  I can't speak for Ansel, but given  
the JOINs that were at issues at the beginning of this thread, and a  
basic understanding of the advanced features of Ansel, it's a safe bet  
to assume that Ansel is one of those applications that benefits from a  
full RDBMS.

As always, as an admin it is your decision on how to locally setup to  
maximize performance based on the local environment.  But as a  
project, it is one of our goals to give admins these choices, as  
opposed to other software solutions that lump all projects, no matter  
the scope, into a LAMP-ish box.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]