i am just curious. and so i request this specific question about SQLite. I've not use this kind of database extensively. but choose to explain what's the fundamental different between SQLite and Mysql ?

The explanation for all this is among the finest to understand whether or not this possible for doing things to keep wordpress data and behave as a database ?

Technically, you should use WordPress with SQLite. Should you not cash traffic it's an option.

It's trivially simple to use a copy of MySQL along with a webserver onto any machine, so when you could use SQLite, it might be much more difficult than getting a duplicate of MySql and setting up it.

WordPress doesn't support not MySQL out-of-the-box, but it's feasible for a database-wordpress plugin to exchange that support with nearly anything, whether it wanted to.

If you wish to test this in your area or something like that, just grab a duplicate of XAMPP and install WordPress on that. Easy.

SQLite is definitely an in-process or desktop class database. MySQL is really a server class database. I am a little well known for marketing server-class engines over desktop or perhaps in-process -class engines for internet sites, because regardless of how you do at the in-process database engine you will have concurrency problems when a lot of people attempt to access your website simultaneously.

However, I believe within this situation you may work with SQLite, as lengthy when you are careful by what plug-inches you put in. This is because you are likely only likely to have one individual upgrading your wordpress blog, and most likely in-frequently at this. In order lengthy as you are careful about using plug-inches that do not reach email the database for each customer, sqlite must do fine.

SQLite is really a file database. There's no running process or anything, it's literally only a regular file in your disk. MySQL is really a full fledged database server, something which needs to be run individually. SQLite is most effective when ever programs require a small database to keep configurations or data.

You could get it done with SQLite, but SQLite is not really intended to be used at the same time (ie, by multiple customers being able to access it at the same time). So unless of course it's some dinky internal site that are only utilized with a couple people, I would not recommend it.