Wednesday, May 30, 2012

Any Good ORM tools for Android development?


Anyone working on the Android ('gPhone') have or know of a place where I can find a good ORM tool for it? The code is written in Java, and the DB is SQLite. What I would like to find is a tool that given the object definition, can auto-generate the tables and the CRUD functions (that would be awesome), or, barring that, a tool that can take the table definition, the object definition, and auto-generate the CRUD functionality. The rub is that all of this must happen within the android framework, which has its own conventions as to how DB access works.



Source: Tips4all

16 comments:

  1. This thread might give you some to explore: Lightweight Alternatives to Hibernate

    ReplyDelete
  2. Thought I'd just add my $0.02 here about my ORMLite package:


    http://ormlite.com/


    It is a lightweight replacement to Hibernate and uses native Android OS database calls to support SQLite on Android. It also supports many other database types using JDBC on other architectures. Love to get feedback if anything is missing for Android developers.

    ReplyDelete
  3. If performance and code size matter, check out greenDAO. I'm the author of it, and my motivation to create another ORM was to avoid reflection in the hotspots. It turned out that greenDAO can be up to 4 times faster than ORMLite. Checkout the feature page for details.

    ReplyDelete
  4. I don't know of anything that is exactly what you are asking for, but there is an alternative to SQLite that you may find useful if your architecture requirements are flexible. It may be worth checking out DB4O:


    Android DB4O
    Code Comparison Examples

    ReplyDelete
  5. I liked ActiveAndroid. It's written specifically for Android it seems. That's feels like a plus to me.

    I have some Ruby on Rails experience and if you like the Rails way of ActiveRecord you can very quickly get moving with this library.

    https://www.activeandroid.com/

    ReplyDelete
  6. ActiveAndroid ($20) looks like it may be exactly what you need.

    ReplyDelete
  7. I'm also looking for an ORM on Android. I tested ActiveAndroid, NeoDatis and Db4o, and I think that I'll use one of the two last.

    NeoDatis and Db4o are really similar, so I would like some advice to choose the best one. Is someone using one of them on his project ? I'll use it for free and paid app, but it seems that the two haven't any license limitation for Android.

    There is a benchmark here that seems to say that NeoDatis is faster than db4o, but I don't know if we can base my opinion on this.

    ReplyDelete
  8. One more newcomer: android-active-record.
    It's very lightweight and easy for use persistence framework for Android backed by SQLite
    http://code.google.com/p/android-active-record/

    ReplyDelete
  9. https://github.com/ahmetalpbalkan/orman

    Orman framework might help you. It is especially designed for that and very small and useful.

    ReplyDelete
  10. ActiveRecordJS from Aptana is a Javascript ORM that should run on the gPhone. It is designed to work with Jaxer and Gears. When you user the Jaxer Adapters, you can connect to SQLLite.

    UPDATE: I don't think I made it clear, but ActiveRecordJS is an ORM that runs client side, which could be an advantage to you on the gPhone.

    ReplyDelete
  11. I have developed my own implementation of the JPA ORM for Android. It is not yet fully feature complete, but you can annotate class with the @Entity, @Id, @Column annotations and you get JPA entities that can be stored and retrieved from the SQLite database. It needs some more features & cleanup before I'll post it to the public, but if there is enough interest it might accelerate my effort.

    ReplyDelete
  12. http://hadi.sourceforge.net

    This tool is very simple and easy to use.

    ReplyDelete
  13. Even though this is an old post, the topic is still relevant. Hence, I want to share an interesting article and nice approach to solving most of the issues mentioned in the question:

    http://blog.codecentric.de/en/2011/04/android-persistence-accelerated-small-inhouse-orm/

    Hope anyone finds this as useful as myself!

    ReplyDelete
  14. I have sat and reviewed all of the ORM's mentioned and I really like Orman so far, the others, especially the meta data driven types are too cumbersome. I just hope Orman continues the great start! One possible limitation with Orman though, is only one Index per table? Seems weak and hopefully it will be addressed.

    ReplyDelete
  15. Had negative experience with db4o (v. 8): indexing didn't work properly (exception etc.). So I didn't managed how to avoid creating duplicates in foreign tables when having object in object structure. More detailed explanation in my question. Hope one day it would be better.

    ReplyDelete
  16. My own DroidParts /http://droidparts.org/ just reached v1.0. It's a DI/ORM library & more.
    Not much documentation, but includes a sample app.

    ReplyDelete