Share your experience using SQLite

I used it for assignments, putting in code, and learning. The course itself provided everything sorted by links, so there were no issues there. If I were working on a new assignment or data system, it would suggest things to me. Unfortunately, I had to switch to Microsoft tech.

It was a bit easy to use compared to other tools.

It's simple. I found it pretty easy to execute my SQL queries. Since I was a beginner, it was comfortable for me to learn SQL using SQLite. However, when I used it for my professional work and for my assignments, I found some complications. Maybe I'm not proficient with it, that's why.

The main benefit for me was learning. Since I was new to SQL, SQLite helped me understand how to work with structured data.

There were some complications. For example, you have to upload the dataset into SQLite, and once it's uploaded, you might find difficulties working with it.

I used it for two to three months. 

I would rate the stability a six out of ten. There is room for improvement. 

Compared to other tools, the performance was less effective than that of Microsoft Access. There were no complications in Access when importing datasets, which is a crucial first step. If you are stuck on the first step, you are not gonna work with it. So, I faced issues importing my dataset into SQLite. Since I couldn't get assistance with SQLite, I again had to switch to Access for my work.

I didn't find SQLite to be reliable. 

I would rate the scalability a six out of ten. Most of my classmates are Windows users, and Windows already provides Microsoft Access. 

Since I have a Mac, I used SQLite. Unfortunately, I faced complications when working on my assignments, so I had to switch back to Access.

I used PostgreSQL. However, I found difficulties using PostgreSQL. 

I had to switch to Microsoft Access because I faced issues while uploading and importing my dataset into SQLite.

The SQL aspect of it is straightforward. The work itself is not complicated.

SQLite was easy to integrate into our development environment.

I learned from videos, and they guided me. It took me about five to ten minutes to get comfortable with it.

Overall, I would rate the solution a six out of ten. I would recommend it. Many people don't have good tools available. If they want to work on databases without using Microsoft Access, then SQLite is a better option for macOS users.

I also tried Oracle and SQL, but it was very hard for me to set them up. SQLite is a simpler choice. My biggest issue was importing the dataset into SQLite. If I could have done that, the rest would have been easy. It has a responsive design and is also visually appealing.

We use SQLite to store data locally within our mobile applications.

We use it for storing data within the local storage of the mobile application. That's its primary purpose.

A potential drawback is that the database file stored within the application's local storage could be accessible to users. 

When you build a mobile application with SQLite, the database file is often included in the assets folder. When the app is installed, a folder is created in the device's local storage. 

In older Android versions, it was possible to access that database file directly from the local storage. I'm not sure if this is still a concern with the latest Android versions like 10, 11, or 12.

I have been using it for three years. 

I haven't encountered any problems in my use cases. So, it has been a stable product for me. 

Usage depends on project requirements. Some applications need local storage, so developers might use SQLite; others might use something like Entity Framework. It varies, and sometimes, client preferences also play a role.

There might be over a hundred end users. 

SQLite was a standard approach for storing data locally in mobile applications. That's the main reason for its adoption.

The initial setup quite simple. You download the setup files from the official source, install them on your Windows system, create a database, and then copy that database file into your mobile application. The process is clear and easy to follow.

SQLite is primarily used for embedded storage in mobile applications.

It is not expensive.

There are both pros and cons to SQLite. 

• On the positive side, it's easy to use. 
• However, a potential drawback is that the database file stored within the application's local storage could be accessible to users. 

You need to consider both the advantages and the potential security concerns.

Overall, I would rate the solution an eight out of ten. I would recommend using it.