Implement a SQLite database at the server end to keep accounts data and measurements for all users. When using a SQLite Database Viewer, your data should appear as the way you design it. For example, I can design a database with two table to keep accounts and measurements as following figures.
You have create a database on your own at beginning and insert at least the default account (name: test, id: 1234) into a table. This account will be used as the default account for testing purpose. You also need to design your database in order to store all the measurements from user.
When retrieving account data or measurements, you have to give SQL command accordingly and get the smallest data set from a SQLite database. Account verification request, Measurement storage request, and Measurement retrieve request in your lab2 assignment should read data from or save data into the SQLite database now.
Tasks for Lab 3:
For lab 3, you are expected to modify some features in your server application and client application from lab 2 and implement a database at the server end to keep all critical data. No skeleton code will be provided this time. You have to use your codes from lab2. We will check following three major functions:
Account verification request
Measurement storage request
Measurement retrieve request
Please make sure all of them will work correctly with a SQLite database.