Just answer yourself: do you really need SQL database? For my game highscore storage I thought about it, and answer was "NO": - I do not have to keep a lot of entries ( maybe 200 - it' enough ) - I'm not sure that my entry will stay the same (upgrading schema is PITA) - Doing "select count" and then remove lates is quite tricky - do I need complicated selects? (Apparently no, sort by score is enough)
So why I do need database? All this requirements are covered by serialized list writen into flat file (or even in preferences) But since I like to submit my highscores to server, I choose to serialize highscore object into JSON and wrote opensource marshaller for this purpose. On Mar 17, 3:05 pm, Hari <mba.for.d...@gmail.com> wrote: > Memory footprint considerations are top priority. However, the > dependency is only 1MB ( db4o-7.4.72.12266-java5.jar ) for Db4O !!!!! > > On Mar 17, 3:10 am, ko5tik <kpriblo...@yahoo.com> wrote: > > > There is some movemet in this: > > -http://groups.google.com/group/androdb-dev-people have started > > work on liteweight ORM tool (not much there yet) > > - I use JSON marhalling to text files > > (functional:http://github.com/ko5tik/jsonserializer) > > - you may dig out xdoclet(2) and create plugin to generate > > databinding layer for you. (ask me how to do this ;) ) > > > I evaluated db4o for middleware, but ended using hibernate instead. > > Main questions with those ORM tools is a size. > > Can you afford 1MB dependency stuffed in your apk? 10MB? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en