Closed timozattol closed 10 years ago
It can be done, no problem.
We still have to keep in mind that the server will be providing an API for storage purposes. So the choice of database technology on the server shouldn't change anything.
Yes, right. But then the server "internal" SQL commands can be reused in the client's database, right ? Anyways, I don't think MySQL and SQLite are so much different.
Progress: VM was set up. see the wiki for connection info. SQLite3 is up and running, Nginx is set up, document root is in /var/www/radin.
We don't actually need internal SQL commands in the server, the framework already has a good API to access the database using objects (encapsulation, type testing...) But if you prefer, we can directly inject SQL statements in the code.
@ireneu okay, cool ! Obviously no, I don't prefer copy pasting SQL commands :P
About that, we might want to set up a SQLite DB instead of MySQL, since
So we might want to store locally (cache), in the phone, the data in a SQLite database. It's certainly better to use the same database on the server and on the phone.