Hello I want to implement Cache Control for a product i'm selling. I'm developing it in php and need help to decide what database will i use, it have to be widely supported. www.wikifetcher.com I think about SQLite, what is your recommendations? Thanks!
Well, if I'd make a product for selling, I would choose the most widespread database. MySQL that is. Any reason not to choose it?
I agree with n0other, if you choose anything *but* mySQL, it will certainly dampen your sales. Most hosting accts come with a free mySQL database, so your customers will not incur any additional expense to setup the software. Although I'm a long time Oracle and SQLServer database admin, I can tell you that mySQL (as well as postgreSQL) are amazingly robust for most web applications - and they don't cost huge $$$ to use I'm a little surprised that a PHP programmer wouldn't consider mySQL straightaway - were you just trying to advertise your URL???
well thanks... my main goal is to make it as simple as it could be, SQLite seems simple because the user does need to configure anything.
Does anyone know how well SQLite scales? I've never used a database besides MySQL with PHP, so I don't have any experience with it.
Probably the best choice as the user wouldn't have to install anything at all. Easiest to develop for and support too. Pretty good I'd reckon. Good enough for caching a decent site probably as it would mostly be read operations. If a site / application is more write intensive I would use a "real" database server such as Postgresql or Firebird but not mySQL as it has no good dataintegrity and very poor SQL standards compliance. But as other posters have pointed out you may just have to support it as it is the most widely used database on webservers. This is from the sqlite website (http://www.sqlite.org/whentouse.html)
At your level, you should start with a free server, mainly MySQL. when you get the needed expertize and you need more flexibility and options/security, you might switch to SQL server.
Did you read what he wrote? He thinks MySQL is overkill and is asking for reasons to use it (et al) rather than SQL Lite.