Question: what's the official (yes/no) on SQLite?

Started by Kaylum, September 14, 2008, 02:10:32 PM

Previous topic - Next topic


hello everyone

this question is for the developers of SMF..

what are your thoughts on using SMF with SQLite vs. MySQL? you provide db creation scripts for both db engines, along with postgres.. but after reading some of the threads regarding issues with SQLite, most of the recommendations were "not to use it".

as of Beta 4 Public, is that still the recommendation?



Not speaking as a developer but I believe that MySQL will always be the core of SMF it is supported and is heavily optimized for MySQL, all current mod's support MySQL and is the most supported environment for SMF support as well.

If your hosting environment supports MySQL I would use it over other database systems..

The other database systems were mainly for users who did not have access to MySQL or preferred to use other database systems other than MySQL.
Community Suite for SMF - Take your forum to the next level built for SMF, Gallery,Store,Classifieds,Downloads,more! -  Paid Modifications for SMF

EzPortal - Portal System for SMF
SMF Gallery Pro
SMF Store SMF Classifieds Ad Seller Pro


Welcome to SMF.

Just to add to what vB has said, MySQL is recommended if you have it. We're working on ensure 100% feature compatibility with the other DB systems.

As for SQLite, it will always be better to use MySQL or PostgreSQL instead as SQLite has many limitations which you will start to notice unless you have a very small site.
Former Support Team Lead
                              I recommend:
Namecheap (domains)
Fastmail (e-mail)
Linode (VPS)


thanks for the welcome.

i'll go with MySQL,. although the thought of using SQLite tickles my fancy, heh.. a final question:

if there is a known limitation that SQLite performs poorly in larger sites (not sure how that is defined, by records?), why was it considered as a possible db engine option?


Sqlite should really only be considered for small sites like on local intranet where you don't need the power of Mysql or Postgresql and only going to have a couple of users using it at once.

Sqlite should not be seen as a realistic substitute for mysql or postgresql.


SQLite has a bit of a novelty factor too ;)

I think the main problem is concurrent users, not database size so much.
"Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise."