converting standard wordpress into a SQLite powered multi user blogging platform

19 thoughts on “converting standard wordpress into a SQLite powered multi user blogging platform”

  1. very helpful and valuable information, Thanks for this boss.

    but if this is work using PDO then it may be also works with other database also (PDO works with a lot likt Microsoft SQL Server , Sybase, Oracle etc )

  2. @arifulnr – yes it would work, but you need to write an adapter object to convert mysql specific queries for that DB again.

    currently the package has adapters for only mysql and sqlite.

    interested in writing one for pgsql?🙂 that would be great!

  3. Thanks Hasin vai for this information, i will google it for that. but i have another problem and need your help. i am now studying your facebook book but i find the facebook application Edit Settings section is changes during last 1 and 1/2 (as you book published may 2008) i works on facebook tools a lot and try it on a real server but fail to configure the the application so that it works on facebook . can you write a post for all of us on configuring facebook application.

  4. from the SQLite website:

    Website Database. Because it requires no configuration and stores information in ordinary disk files, SQLite is a popular choice as the database to back small to medium-sized websites.

    If your blog becomes bigger you should use MySQL… I don’t think there is something wrong with the default WP setup

  5. Hi Olaf

    Yeah, MySQL is best choice for a bigger blog, but still, i think SQLite still will be able to manage quite a load.

    And by the way, SQLite is able to handle moderate load in a medium level of concurrency.

    Porting WP to SQLite is fun🙂 – so it’s just a fun project🙂

  6. There are a number of reasons why a user might want to use SQLite in place of mysql. Off the top of my head:

    1. portability (just pick up the sqlite file and go)
    2. backup (no db scripts, just ftp the sqlite file)
    3. their host has a generous file space limit but lousy mysql limits (1 & 1 uk for example, on my package, allows gigs of file space but only 100MB of mysql db).
    4. running the blog on a NAS or hacked router which is underpowered for running mysql
    5. looking for a really low memory footprint

    there are probably more …

    i am running into issues bringing PDO for WordPress up to speed with 2.9 at the moment. i am going to have to play quite a bit with the install routine which is aggravating.

    a fellow internaute has written a driver for MSsql if anyone is interested. i suspect that the SQLite driver will work fine for postgres. not tested though. perhaps the create statement rewrites might need a bit of tweaking.

    on benchmarking: we do a lot of PCRE work on queries, and PDO is much less efficient than native mysql_* calls (in most cases), so we are overall slower the native. SQLite benchmarks on its own very close to mysql for normal-mid-range applications, however. I have not noticed any major performance problems on any of my sqlite blogs, but then again the internet latency is so long compared to programme execution that it hardly matters until your site gets _really_ busy!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s