[UPHPU] Re: SQLite - Is it a strong alternative?

[Lonnie Olson]

On Jul 31, 2006, at 8:13 AM, cole at colejoplin.com wrote:
> For web, multi-user access could be a problem, even for a business  
> app. So, I really wouldn't use it for that. I'd just run with  
> MySQL, because that's exactly what it was designed to do.

SQLite can be a strong alternative depending on your requirements.   
If you need a fairly simple, small, portable database, SQLite can be  
a good fit.

SQLite can handle multi-user access.  When a write is necessary the  
whole database is locked, but only for a fraction of a second,  
(SQLite 3 is even better at this).  During the lock any requests will  
just wait.  As long as your website doesn't get swamped with writes,  
it can handle a whole lot of traffic.  Don't expect to use SQLite for  
a site like digg or slashdot, but *do* expect to be able to use  
SQLite for moderate traffic sites.

To learn more about SQLite in general see
http://uphpu.org/article.php?story=20060417120636607
http://www.sqlite.org/
http://www.php.net/sqlite

--lonnie

> Quoting "D. Turnbull" <turnbud at gmail.com>:
>
>> SQLite is an interesting alternative, but it has some limitations.  
>> Last I
>> used it (about a year ago), it supported foreign-key syntax  
>> without actually
>> supporting foreign keys (I ended up simulating foreign-key  
>> behaviour with
>> stored procedures). And because its databases are simply files, it  
>> locks the
>> entire database every time you write to the file (meaning nobody  
>> can read
>> from the database until the write is done) -- of course, this  
>> means the
>> databases are uber-portable.
>>
>> As to whether or not its a good alternative for you, only you can  
>> know that.
>> Search your feelings, there is good in you yet . . . use the  
>> SQL . . . and
>> so forth.
>>
>> Dave
>>
>>
>> Subject: [UPHPU] SQLite - Is it a strong alternative ?
>>>
>>> I'm getting more and more convinced that simpler is better and  
>>> usually
>>> more successful.  I appreciate the intro presentation we had several
>>> months ago.    The whole issue of low maintenance, easy backup, easy
>>> transportability  etc seems very appealing.  In that light  
>>> (lite?), can
>>> SQLite really be used as a replacement for Postgres or MySQL  for  
>>> a php
>>> driven web app ?   Has anyone here really put it to the test that  
>>> way
>>> ?   We're not talking a massive consumer web service a la  
>>> MySpace, just
>>> a normal business app.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2593 bytes
Desc: not available
Url : http://uphpu.org/pipermail/uphpu/attachments/20060801/0d3eeff1/smime.bin