NoSQL

[thePeras]

Closes #1391 closes #755

Used Object Box, which is not the ideal approach since it require new annotations on models and don't rely on the existing serialization.

Bus stops remain in sqlite since they are not working and fix code need to be written.

Comparing SQlite and NoSQL

I run a simple experiment to compare the read and initialization times with my personal Exams data (around total 8 exams)

• The read values are the mean of 5 experiments with the DB already up.
• The DB initialization values result from 3 experiments, no schema migrations involved.

---	DB initialization	Reads
SQLite	19ms	15ms
ObjectBox (NoSQL)	161ms	2ms

Note: The NoSQL db initilization already opens the file used for all models where the SQLite only opens the Exams database

Conclusion

Since we had 9 databases and assuming they all boot up the same time as Exams, sequentially all of them would make 171ms to set up. Base on that, both of the technologies have similar db initialization times for a scenario using all the models (example: homepage with all of possible cards). However, read times were significantly decreased.

[thePeras]

As discussed in meeting:

• Close and use isar, remove library ocupation database and move Profile to PreferencesController temporary.

• Some things of PreferencesController should migrate to database, and Preferences is for Preferences, no more than that.

• Implement in just one file, database

[thePeras]

Currently with two files implementation.
Next Step: Join everything in a single singleton class called Database. ✅

[thePeras]

Configured the Database Interface and added instructions to view it in the readme.

[codecov]

Codecov Report

Attention: Patch coverage is 3.92571% with 2276 lines in your changes missing coverage. Please review.

Project coverage is 9%. Comparing base (155dda9) to head (216e728).
Report is 650 commits behind head on develop.

❌ Your project check has failed because the head coverage (9%) is below the target coverage (70%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #1411    +/-   ##
========================================
- Coverage       12%      9%    -2%     
========================================
  Files          265     252    -13     
  Lines         7397    7234   -163     
========================================
- Hits           819     650   -169     
- Misses        6578    6584     +6     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[abutuc]

Looks good! Watch out for the changes made in the restaurant_page_view, might cause some conflicts due to the redesign developments.

[thePeras]

Looks good! Watch out for the changes made in the restaurant_page_view, might cause some conflicts due to the redesign developments.

Good Point! I think I should wait for redesign to be merge on develop or change the origin branch to ui/redesign

[thePeras]

One model was updated, I don't remember the one. The restaurant?

[HenriqueSFernandes]

Missing feature:

• Schedule changes (depends on Add Professor Picture to Schedule Card #1530, closes Update NoSQL implementation due to new changes into models #1539)