Creating the DAO object should fail if the schema doesn't match. It's when you start doing db transactions is when you might get exceptions.
There are many ways that you could manage your schema changes:
- You could store a database version in some meta table (like android) and then apply schema changes if the version < code version.
- We do a similar thing by store schema changes in numbered files. Whenever our application boots it sees whether all of the schema change numbers have been applied and if not it applies the schema changes in order.
Anyone else have recommendations?
gray
> --
> You received this message because you are subscribed to the Google Groups "ORMLite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ormlite-user...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.