Quote:
Originally Posted by shake
I'd avoid using sqlite if you can avoid it. There are better options like Postgres or even mySQL. Unless you really need just local storage only.
|
I have a lot of experience with sqlite so i can give precise instructions when to use and when not to use it.
So, first when not to use it:
1.If you have multi-user app/script . I made a mistake by using sqlite for my tracker script, and as result i had often deadlocks which caused script to be unresponsive and lost some $$$ due that until i finally switched to mysql.
When to use it:
1.If you have single user app/script. For example, i have script which i developed 10 years ago and i am only user and so far it works without any bug/error.
And advantages of sqlite compared to mysql -
1. Does not require username/password
2. Easy to backup/have only one file
3. It can be encrypted easily for free