[horde] Fwd: installing ansel 2.0.2

[Michael J Rubinsky]

Mailman ate the email again due to S/MIME signature. Forwarding...

----- Forwarded message from Michael J Rubinsky <mrubinsk at horde.org> -----
     Date: Fri, 17 May 2013 15:28:17 -0400
     From: Michael J Rubinsky <mrubinsk at horde.org>
Reply-To: mrubinsk at horde.org
  Subject: Re: [horde] installing ansel 2.0.2
       To: horde at lists.horde.org

Quoting Michael M Slusarz <slusarz at horde.org>:

> 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.

Sure. I can agree with this. I was talking about using sqlite as the  
sole database to use with Horde. Using something like sqlite for  
smaller subsystems makes much more sense than using it globally. E.g.,  
using it with Ansel, or Kronolith on a large install and having it  
churn through all the share, perms, tagger queries...

> 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.

Agreed, and is one of the reasons I put so much effort into optimizing  
the tagger queries when testing with sqlite back in the day.
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org

----- End forwarded message -----

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
An embedded message was scrubbed...
From: Michael J Rubinsky <mrubinsk at horde.org>
Subject: Re: [horde] installing ansel 2.0.2
Date: Fri, 17 May 2013 15:28:17 -0400
Size: 14664
URL: <http://lists.horde.org/archives/horde/attachments/20130517/d2a56aa0/attachment.mht>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20130517/d2a56aa0/attachment.bin>