Both have an embedded version, so the memory footprint would be smaller in both cases.
DB4O is open source and has a java api. I think ExtremeDB is C/C++. You can visit the following links for more info: http://www.db4o.com/about/productinformation/db4o/ http://www.mcobject.com/standardedition.shtml take care, Muthu Ramadoss. http://linkedin.com/in/tellibitz +91-9840348914 http://androidrocks.in - Android Consulting. On Thu, Mar 12, 2009 at 12:01 PM, Sena Gbeckor-Kove <[email protected]> wrote: > Any idea which is faster and which has a smaller footprint? db4o or > extremeDB? > S > > > > On 12 Mar 2009, at 03:19, Muthu Ramadoss wrote: > > It just happened the content providers were using the bare bone sql > approach for their early versions. Future versions might provide ORM as an > alternate persistence strategy within content providers. But given the > current design you are ofcourse free to do whatever in your implementation, > including using dbo or otherwise. > > take care, > Muthu Ramadoss. > > http://linkedin.com/in/tellibitz +91-9840348914 > http://androidrocks.in - Android Consulting. > > > > On Thu, Mar 12, 2009 at 6:14 AM, Sena Gbeckor-Kove <[email protected]> wrote: > >> Will it actually simplify content providers I though there was some reason >> why we can't use object persistence on them. >> S >> >> >> On 11 Mar 2009, at 18:29, Muthu Ramadoss wrote: >> >> Wow, this is going to really simplify the content providers. Thanks >> German. >> >> take care, >> Muthu Ramadoss. >> >> http://linkedin.com/in/tellibitz +91-9840348914 >> http://androidrocks.in - Android Consulting. >> >> >> >> On Wed, Mar 11, 2009 at 10:49 PM, German <[email protected]> wrote: >> >>> >>> Hi. >>> >>> For those of you who never heard about db4o -> it's an Android >>> complaint open source object database with a thriving user community >>> (http://developer.db4o.com). It allows you to store/retrieve POJOs >>> directly (no tables, no rows, no cursors) without sacrificing speed, >>> flexibility and reliability. >>> >>> I'm sending this message to the list because I wanted to let you know >>> that we've updated the PasswordSafe and MapMe Android demos to work >>> with both the latest stable version of db4o (v7.4) and Android SDK >>> (v1.1 r1). >>> >>> By checking out these examples (tutorial and videos included) you'll >>> realize how easy and straight forward it's to persist POJOs rather >>> than relying solely on SQLite. >>> >>> For more information see: >>> >>> http://developer.db4o.com/blogs/community/archive/2009/03/11/db4o-android-demos-updated.aspx >>> >>> Enjoy!! >>> >>> German Viscuso >>> db4objects >>> >>> >>> >> >> >> >> >> >> >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
