I would like to confirm that SQLite allows: 1. Big database 2. Big number of fields 3. Complicated queries 4. Very fast
but not 1. High concurrency The problem is there is a lot of PHP applications require MySQL or PostgreSQL backend. SQLite is very fast for tasks with low concurrency. It will become a bad option when you decide to roll out a high-traffic website and/or a website that need to serve multi-users browsing at once. By nature, it locking mechanism does not fit for it. Moreover, PHP is moving toward to be a tool for web applications that require high concurrency and scalability. On 12/17/06, Chris Hartjes <[EMAIL PROTECTED]> wrote:
I beg to differ about PDO + Sqlite. File-based solutions like SQLite have their place if you're creating large databases with small numbers of fields and don't need to do any complicated queries. -- Chris Hartjes "The greatest inefficiencies come from solving problems you will never have." -- Rasmus Lerdorf @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard
-- Nobody in nowhere
