Multi-user applications:
If you are working on an application whereby multiple clients need to access and use the same database, a fully-featured RDBM (e.g. MySQL) is probably better to choose over SQLite.
Applications requiring high write volumes:
One of the limitations of SQLite is the write operations. This DBMS allows only one single write operating to take place at any given time, hence allowing a limited throughput.**
next course of action: I am going to setup mysql for our database.
-tried to install mysql in the virtualenv that was setup with sqlite3 but I get an error because it can't find the mysql file. I have tried the fixes from stackoverflow with no luck.
-I am setting up a database on mysql workbench. -we can export it to our aws server or whatever server we decide to use
When Not To Use SQLite
Multi-user applications: If you are working on an application whereby multiple clients need to access and use the same database, a fully-featured RDBM (e.g. MySQL) is probably better to choose over SQLite.
Applications requiring high write volumes: One of the limitations of SQLite is the write operations. This DBMS allows only one single write operating to take place at any given time, hence allowing a limited throughput.**
next course of action: I am going to setup mysql for our database.
-tried to install mysql in the virtualenv that was setup with sqlite3 but I get an error because it can't find the mysql file. I have tried the fixes from stackoverflow with no luck.
-I am setting up a database on mysql workbench. -we can export it to our aws server or whatever server we decide to use