我是否需要SQLite才能在MySQL数据库上存储一些数据

Question

If I need to store some data on MySQL database, should I first store it on SQLite then sync SQLite on Android to MySQL database?

Is it possible to store the data to MySQL database without having SQLite ? If yes, what's the better option ? (with SQLite or without it)

update
I need MySQL becase I want person1 to be able to see person2's data, which is not possible if person2's data was stored on SQLite, because it will be sitting in person2's Android device.. am I right?

Answer 1

The question is where do you want to put your database ? If in-app then there is no other choice but SQLite.

If it's off-app then the possibilities are limitless. You can run your own server and MySql database for sure. If you use cloud solutions like those offered by Amazon AWS for example, you won't even need to setup a server because they have SDK that allows the app to communicate directly with the database.

Syncing strategy depends on your app. Maybe it is not needed and your app can send queries to your db on demand basis. My rule of thumb is I resist setting database in the client or app. Why ? Because once it's there, modifying it won't be easy. Plus it's at the mercy of settings->clear data or uninstall.

If you want to do what your edit says then you need to do it off-app. You need a central database that collects data from all installs and allows queries from them. I need to emphasize that if it's off-app it doesn't need to be MySql. MySql is just a kind of relational database system. You can use schemaless systems (or NoSql), file storage (if the data are files), etc which all depend on many considerations.

Answer 2

Android only supports SQLite database which will be sitting in your app on the Android device.

If you want to use a MySQL database you will need to create an API that will be sitting on a server somewhere on the internet. This API will create an interface from your application to the MySQL database. You will then need to make network calls to your API from your Android App.

There are loads of options using an API model so really you will need to do some Googling and work out what works best for you.

Edit

To answer your edited question, you will definitely need to have a design pattern using an API. If you are creating a service that needs to be accessed from multiple devices then it is usually the way to go. The benefit of using an API is that they can be used cross-platform. So not only will you be able to use it on an Android device, you may be able to use it via the Web, IOS app etc...

A simple and typical architecture to get you going is that you have an Android App which will send network calls to an API over the web via HTTP. The API will be sitting on a server that may have a MySQL database stored on there. The API will authenticate your user and carry out the method required which will probably do some database query. Once the API has the results, it will send it back to the Android App which will be parsed and displayed to the user.

It's a massive topic so really you need to do a bit of research on this one.

Answer 3

Android does not support MySQL to save application data, as you can see mentioned on the developer.android website.

Although, you are not compel to use the SQLite Database to be able to comunicate with other RDBMS. You can see this example, that shows you how to retrieve a data records from a remote MySQL database using JSON, PHP and HTTP requests.

I think that you can also have a look at ContentProviders . They are usually used with SQLite but I think that it may work with other RDBMS.