That's what I feared. I was hoping the cursor was only keeping primitive references to the data in the db file.
If I'm going to be doing many smaller queries & keeping the results around, sounds like I might as well keep the objects myself. Lets me index across the varying data density also. There's still the lifecycle handling -- if I have this ArrayList, and I want to keep it across rotates, I could keep it in a static. The trick is knowing when to release/null it. First thought is to set a flag in onRetainNonConfigurationInstance, otherwise I'll release it if the flag isn't set when onDestroy comes along. Seem reasonable? Very helpful dialog, I appreciate everyone's time & cycles. Tim -- 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
