With the migration to sqflite to v4, it's now no more possible to use sqflite capabilities like migration stuff (but more than migration, the lifecycle of the database is now hidden and not accessible).
I think we should still pass the sqflite database to the adapter like we did before, it allow users to do stuff before setting up jaguar.
Concerning database migration: Which solution of the following would be better?
Provide a possibility to handle the migration via the SqfliteAdapter, e. g. by passing an 'onUpgrade' and 'onDowngrade' function.
Create a DB migration solution directly within the Jaguar ORM library that is independent of the underlying DB adapter and thus would work with every database.
With the migration to sqflite to v4, it's now no more possible to use sqflite capabilities like migration stuff (but more than migration, the lifecycle of the database is now hidden and not accessible).
I think we should still pass the sqflite database to the adapter like we did before, it allow users to do stuff before setting up jaguar.