This is a large api change intended for SquiDB 2.0. The basic idea is to merge the responsibilities of AbstractDatabase and DatabaseDao into a single, unified class called SquidDatabase. This has several benefits:
The fact that DatabaseDao wrapped an AbstractDatabase subclass made it hard to know what kind of database you were talking to, especially in apps with multiple databases. Now, all that's required is to subclass SquidDatabase instead of AbstractDatabase--that part of the api remains the same. But now, you can now talk directly to your SquidDatabase subclass for all database I/O, which means you always know what kind of database you're talking to.
You can define custom database access methods directly in your database subclass using dao methods without also needing to create a subclass of DatabaseDao
Dao methods that work with model objects are now easily available from hooks like onUpgrade() and onTablesCreated().
Further changes intended for SquiDB 2.0 will build on this foundation.
jdkoren
commented
9 years ago
This is a large api change intended for SquiDB 2.0. The basic idea is to merge the responsibilities of AbstractDatabase and DatabaseDao into a single, unified class called SquidDatabase. This has several benefits:
Further changes intended for SquiDB 2.0 will build on this foundation.