Higher level database layer for Android?

Question

Are there any good database abstraction layers/object relational mappers/ActiveRecord implementations/whatever they are called for Android? I\'m aware that db4o is officiall

Answer 1

Shameless plug, but I've been working on a new open source Android framework called Infinitum. One of its main features is an ORM which has a criteria API similar to Hibernate and a few other nifty features (associations, lazy loading, etc.). It's still in its early stages, but I think it's coming along pretty nicely.

Answer 2

I was comparing basics of ormlite and greendao some time ago. You might want to take a look there. I plan to write some follow up with more advanced stuff in the near future but for now it's only a basic stuff. In my own project I'm using GreenDAO.

Answer 3

I am the main author of ORMLite which was designed to be small[ish] but still provide higher level functionality. ORMLite makes calls to the native Android OS database APIs to support its ORM functionality. See the following for general information

http://ormlite.com/sqlite_java_android_orm.shtml

Here are some Android example applications:

http://ormlite.com/docs/android-examples

Answer 4

I tried the Sugar ORM, which is very basic (and easy to use) but it worked for my needs.

Sugar website

Answer 5

If performance and size matter, you should have a look at our open source ORM tool greenDAO. We wrote it because we did not want to compromise on speed. Other tools heavily rely on reflection, which is very slow on Android. Despite the tiny size (<100k), it supports relations, query builders, etc.

Answer 6

There's also Neodatis and Perst (Lite).
I've toyed with Perst a year ago and concluded it's not worth it.
After all, a) Android runs on a rather restricted device with ~16mb of heap space per app and b) You customers would really appreciate performance and low power consumption.
So my advice is to go with SQLite and hand-written SQL. It's not hard at all and the wrappers provided by Android SDK are really nice.

EDIT: In 2012 the advice would be to use the ORM component of DroidParts (which is my project).