Note that getLocalContentProvider is API level 5.
Thanks for the information!! I didn't pay attention to this... :p
I will use the static as you suggested!
Thanks for all time passed to discuss with me.
--
You received this message because you are subscribed to the Google
Groups Android
Well, something is not working :) Possibly something, somewhere, is keeping
references to the old SQLiteDatabase object that in turn still references
the old file.
That is what I think but where between: Content provider | CursorLoader |
CursorAdapter | something else...
If your server
07.08.2011 17:53, CocoRambo пишет:
All case, I am really want to understand the actual behavior
At this point, I would copy the source for SQLiteOpenHelper into the
project (changing the package name, of course) and debug into its close
and open...
--
Kostya Vasilyev
--
You received this
It doesn't seem bad to me at all.
Note that getLocalContentProvider is API level 5.
If this was my code, I'd take advantage of the provider being local, and
keep a reference to the database somewhere (in a static variable). The
provider would use this static to access the database.
In the
I finally find a solution but I am not proud of it...
My mistake was that I called close() on the wrong SQLiteOpenHelper.
So I add a public method to my ContentProvider to get his
SQLiteOpenHelper...
Next during update I do this:
MyContentProvider cp = (MyContentProvider)
5 matches
Mail list logo