Re:A Web Developer Goes Native (with Android)
by mbleigh on Monday September 13, 2010 @01:47PM
(#1687450)
I am aware of SharedPreferences, and serialization is certainly an option, but ultimately these don't solve the main problem I've experienced. Serialization requires a lot of manual work and it may not scale particularly well for middle-weight and up. I just think that the kinds of data stored in mobile applications lend themselves more to some of the various NoSQL patterns than something like SQLite.
[ Parent
| on HN ]
Re:A Web Developer Goes Native (with Android)
by asher on Tuesday September 14, 2010 @12:55AM
(#1689524)
Can't you treat SQLite as a key-value store? Create a table with two columns: key and value. Blobs can be pretty big.
Seems to me that a relational DB can easily impersonate a hash, but not vice versa.