Related to this (but not directly an answer), if you search the Android developer's mailing list, you'll find that there have been a couple of discussions about ORM's in Android. DB4O was mentioned as an alternative (i.e. why use a database at all).
IIRC, there was some discussion as well about the extra overhead required for an ORM. The premise was that on a server running on big iron the overhead was relatively minimal, but on a phone with limited RAM and processor and battery life (which is impacted by a busy processor) it might not make sense to use an ORM. On Tue, Oct 18, 2011 at 03:03, Builder <[email protected]> wrote: > Hello "Mono for Android" developers, > > I'm searching for ORM working with Mono for Android and Sqlite. So far I > found the following ORMs working with MonoTouch: > Vici CoolStorage (works good, API is not so cool) > Catnap-ORM (very nice API, unable to run it, missing any example how to use > it with Monotouch) > Sqlite-net (Unable to compile its source code) > Entify (still beta version) > > I have the filling that no one of these ORMs is mature. Which one of these > ORMs (or even other) do you use together with Mono for Android? Any > suggestions, satisfactions or complains regarding these ORMs are welcome! > > Best Regards, > Peter > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/ORM-for-Mono-for-Android-tp4912963p4912963.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > -- http://www.opgenorth.net
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
