Interesting. Currently I don't use an ORM in my projects solely because if I don't use a CursorAdapter, it's not going to perform well. In addition, we have a fairly large dataset (for a mobile device) that I don't want to have to pull in memory like most ORMS do. If I were able to use an ORM for just saving and updating, then have the ability to also to make a query with a query builder and then use a cursor adapter, that would be a slam dunk for me.
I used OrmLite for Android [1] pretty extensively in a project this spring. I'm not too fond of the DAO pattern, but it did the trick. I ended up using cursors and query builder where it was needed (large lists and such), while using OrmLite for basic CRUD operations.
Certainly more elegant than the SQLite API. Wonder how ORMAN compares though.
[+] [-] darrenkopp|14 years ago|reply
[+] [-] martinp|14 years ago|reply
Certainly more elegant than the SQLite API. Wonder how ORMAN compares though.
[1] http://ormlite.com/sqlite_java_android_orm.shtml