ORMLite is a lightweight DAO layer which most importantly supports Android SQLite. It would help us greatly simplify the codebase, specially the various DAOs.
There are other ORMs (like JDBI, MyBatis, etc) but they don't support Android, they work on only JDBC instead. ORMLite is the only one that supports Android.
The only problem is, we are using SQLCipher instead of SQLite, which has the exact same methods as Android SQLite, but unfortunately its class/package names are alone different.
This spike is to:
Use maven-shade-plugin to rename the class names from android.database.sqlite to net.sqlcipher.database
Spike creating a DAO (either ChildDAO or EnquiryDAO) using the ORM. The best place to inject and check out this temporary DAO would be the ApplicationInjector.
Check if there are any blockers, and specify whether it is possible to implement ORMLite in the codebase or not, so that we can promote this spike into a real story
ORMLite is a lightweight DAO layer which most importantly supports Android SQLite. It would help us greatly simplify the codebase, specially the various DAOs.
There are other ORMs (like JDBI, MyBatis, etc) but they don't support Android, they work on only JDBC instead. ORMLite is the only one that supports Android.
The only problem is, we are using SQLCipher instead of SQLite, which has the exact same methods as Android SQLite, but unfortunately its class/package names are alone different.
This spike is to:
android.database.sqlitetonet.sqlcipher.database