In favor of Sqlite

Hardkap » Pritlog - Blogging made simple

In favor of Sqlite

(8 posts) (3 voices)

Started 2 years ago by Prit
Latest reply from Prit

Tags:

plans

Prit
Pritlogger

I am again thinking on the lines of Sqlite. Reading through the last thread where we discussed about this, the most concerns came because Sqlite may cause additional complexity to Pritlog, there may be additional setup required etc.

Firstly, I request you all to test out the below code on your servers and post the results. You have to extract the below file, upload to your server and run.

http://hardkap.net/pritlog/sqlite1.zip

Edit: I tested this script on some of the most common/popular free php hosts and it worked without any changes:
110mb
000hosted
freehostia
000webhost
007sites
07x

My reasoning:

Not complex at all - Sqlite creates a single file for a DB where Pritlog can store the posts. No additional setup or installation procedure is required. It would be the same as giving the right permissions and run Pritlog.

Portability - One advantage I personally use and enjoy in pritlog is its portability. The folder can be copied to any server, any subdirectory, any website and it will run without any changes or expore/import of databases. Since Sqlite will create 1 file for the posts, Pritlog would continue to be highly portable.

Performance - Since Sqlite is a database, the performance would be awesome even if the number of posts on your blog gets huge.

Posted 2 years ago #
john
Member

test results:

Option 2
Fatal error: Cannot instantiate non-existent class: sqlitedatabase
in sqlite1.php on line 26

My understanding is that SQLite is only available on hostings that installed the SQLite extension.

My provider offers both php 4.3 and 5, but due issues with one script I'm currently on php 4.3. Maybe SQLite is available under php 5. I'll check.

Posted 2 years ago #
john
Member

Switched to php 5, results >

Option 1
Hurray! Sqlite works.

Ok Prit ready for testing :)

Posted 2 years ago #
Prit
Pritlogger

Hey .. thanks for testing John.

From what I read, I think Sqlite will be mostly present if the server is running PHP5. In some servers it is even present with PHP4.

If it is not tedious to do so, would it help to convert the problematic script that you have to use PHP5?

Posted 2 years ago #
john
Member

I already fixed it to stay on PHP5.

I'm just reading some documentation at SQLite's official site (www.sqlite.org)
The following paragraph is interesting:

"SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic."

"Another way to look at SQLite is this: SQLite is not designed to replace Oracle. It is designed to replace fopen()"

Posted 2 years ago #
Prit
Pritlogger

Exactly .. this explains why Sqlite would be a perfect replacement of files for Pritlog. Thanks John. Good find. :)

Posted 2 years ago #
Bert
Member

Okay, if Sqlite is the best way to go, I think you need to introduce a 'Pathfinder', so that mere mortals will be able to install, move, re-install their blog. It's the 'path' thing that creates anxiety, at least for users like me...;)

Posted 2 years ago #
Prit
Pritlogger

Hi Bert .. Which is the path you are talking about here? If it is the path to the Sqlite database that Pritlog will use - then this can stay in the same directory as the Pritlog folder.

Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.