On 12 May, 22:53, Christine <[email protected]> wrote: > 1. where you open and close depends on your app. You can keep the db > open, and close and re-open in onResume and onPause, or you can open > and close before and after you access the db.
ok I know I can ;] but it was more question about performance and design ;] as I didnt see any close call in tutorial I assumed It is handled by the system somehow but then I got exceptions so I was wondering > 3. just retrieve the data that you need in the getView of your list > adapter, don't retrieve complete tables if you don't need them. Of > course, it depends on your app and on the size of the table whether > you want to keep the table in memory or not. so the answer is to handle data fetching from db by myself when user interacts with the view ok, I think I can leave with it -- 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
