When should I and should I not use SQLite?
I have a project where I intend to do but I have no idea how many tables will be, but I believe more than 15 with about 1,000 rows in some tables.
Would it be feasible to do with SQLite?
SQLite you use if you have the need to have a data scenario in disconnected mode.
Example: You have your corporate system (15 tables with 1000 records each), but you need to go to the field (disconnected environment) using an application with data from your system.
So you create an SQLite base on the device that goes to the field (mobile, laptop, etc.) and brings to that database only data that will meet the need for this trip to the field. And as soon as this device returns to the corporate network, you create a logic of timing to bring the SQLite data back to the main database.
Translated from StackOverflow.
SQLite is when you build a java app and do not want to connect with additional database, SQLite can serve as a light db to store your local data
When you app have not access to online services you can use SQLlite, last you need update data with the repository central to maintence the data updated.
De acuerdo a las especificaciones de SQLite, el tipo de base de datos que indica sin problema la puede manejar, obviamente siempre hay que considerar el espacio de almacenamiento, la cantidad de memoria y la capacidad de procesamiento del dispositivo en donde se tenga la base de datos para tener una grata experiencia de usuario al usar la aplicación que utilice esta base de datos.
SQLite is lightweight database. You can use it small desktop/mobile applications where data volume is less. Also you can use it as staging database in mobile application where you want your user can work offline and later sync it with actual database.
3 people are following this question.