It would be awesome if this would do the following things:
1) Generate a DB Helper which would (with some help somehow, very hand-wavey)
generate a SQLiteOpenHelper that will create the database migration (for
onUpdate) ala Rails migrations.
2) Generate one class which will encapsulate loading/saving an object or
collection of objects. Add a simple BeanHelper interface which will provide
the populate/getvalues in a common name, and then treat all objects like this.
In this way, the common database upgrades are already handled by generated
code, creation is generated from the available object types, and I can save an
object by calling one function (akin to Hibernate's .save)
Original issue reported on code.google.com by thatsnot...@gmail.com on 21 Jul 2010 at 1:29
Original issue reported on code.google.com by
thatsnot...@gmail.com
on 21 Jul 2010 at 1:29