Android: Managing cursor passing to CursorAdapter

Question

On Ice cream sandwich, my application starts force close when I wanted to resume the application that has a gridview with a CursorAdapter that have passed in a managedQuery to a CursorAdapter. The Exception would be StaleDataException that saying I am attempting to access cursor which is being closed.

I used the getContextResolver().query instead of using managedQuery. The help me stop having force closed of the applicatio when i tried to resume the application.

In that case, if I used this way. Do I need to close the cursor or will it be closed by Adapter.

Please, please, please don't use `managedQuery`. [Read here to understand why](http://www.androiddesignpatterns.com/2012/07/loaders-and-loadermanager-background.html). — Alex Lockwood, Jul 17 '12 at 03:26

sandrstar · Answer 1 · 2012-07-17T03:42:10.800

1

As per Activity documentation using managedQuery You don't need to close the cursor manually, but using ContentResolver manually You will need to do so. Adapter won't close the cursor, because it doesn't know (instead of Activity) when user left application and cursor is no longer needed. Usually it might be enough to call changeCursor() with null (adapter will close old one) or swapCursor() with null (and close returned cursor manually).

But I would suggest to take a look at CursorLoader as more handy, reliable and suggested by Google way to load cursors. Consider using support library v4 if You're targeting old Android.

edited Jul 17 '12 at 03:42

answered Jul 17 '12 at 02:54

sandrstar

12,503
8
58
65

I look at it before but the support package only work from v3.0 and above of Android. – LittleFunny Jul 17 '12 at 03:14
2

No... it goes back to Android 1.6 (SDK 4) – Alex Lockwood Jul 17 '12 at 03:21
Oh i mean certain libraries in the package. – LittleFunny Jul 18 '12 at 05:30

Android: Managing cursor passing to CursorAdapter

1 Answers1