Agreed. What is the benefit of putting the data in a database, then? If it is sooooooooooooo private that you can't trust it to the on-board flash, don't write it to the on-board flash, and just keep it in RAM.
You could also implement some sort of timeout, where you flush the cache in RAM after such-and-so period of inactivity, re-retrieving the data later, in case the application is merely stopped (e.g., user presses HOME). On Tue, Nov 2, 2010 at 1:54 AM, Chris Stratton <[email protected]> wrote: > What makes you think they can't look in there while your app is > running? > > Seems to me you are just uselessly burning nand write cycles. > > On Oct 27, 8:13 pm, swgillan <[email protected]> wrote: > >> My solution right now is to clear the particular tables I don't want >> people seeing in the database in onDestroy (when the user exits), or >> more accurately in onPause() with isFinishing(). Every time the >> application is launched the database is repopulated, so I am not >> worried about losing any data. I do realize that this isn't foolproof, >> but it seems to be better then nothing. > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming Books: http://commonsware.com/books -- 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
