Hi Alan, I have an almost identical problem. What approach did you take after all ?
So far I'm thinking of: - use a common table for the fields of the superclass, and a table for each in subclass (the subclass fields). This is overkill. - flatten the subclass fields and put them in the database as byte[] - here I'm not very clear if I should use serialization or parcelables Thanks, H On Apr 15, 9:59 am, Alan Jones <[email protected]> wrote: > Hi, > > On Apr 14, 4:27 am, "nEx.Software" <[email protected]> wrote: > > > You could use an object-oriented database such > > ashttp://www.db4o.com/android/, > > of course this one requires GPL. > > Interesting link, thanks. Though at this stage I won't be releasing > this under GPL so > that's not an option yet. > > Does anyone have suggestions regarding this? Information on overhead > of serializing would > be hugely helpful in deciding how to approach this. > > Cheers, > > Alan. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
