There is an old entry on Stackoverflow about SQLiteDiskIOException:
http://stackoverflow.com/questions/3220482/sqlitediskioexception-in-android
It also mentions the getCount method
On Friday, August 2, 2013 6:55:53 PM UTC-5, Nathan wrote:
I have got back two nonfatal exception reports. I
Oh my... when I think about that, I have a pretty old first generation
Samsung Galaxy S (I9000). Its internal storage memory seems to be dying and
quite a few apps behave erratically, including crashes and data loss.
Sometimes it's stuck in an infinite reboot loop. So I'm pretty sure it
won't
I have got back two nonfatal exception reports. I can't match them to any
particular user yet.
When attempting the open.
android.database.sqlite.SQLiteCantOpenDatabaseException unknown error (code
14): Could not open database
From:
SQLiteDatabase.java line
How are you handling transactions in your queries? In later versions of
Android SQLite writes by default temporary journaling data files that are
not immediately merged with the actual database file (see here:
http://www.sqlite.org/tempfiles.html). This might be an explanation for the
reported
On Wednesday, July 31, 2013 9:21:59 AM UTC-7, Nobu Games wrote:
How are you handling transactions in your queries?
A single record written is done as a single transaction. I believe, though,
that the writing part is all done and it is now just reading. No
transactions on reading.
In
Just another related thought: SQLiteDatabase contains some implicit
transaction magic under the hood which is meant to prevent accidents
due to simultaneous accesses from different threads. That does not always
work that great and can lead to some kind of indefinite deadlock situation.
You can
Just another related thought: SQLiteDatabase contains some implicit
transaction magic under the hood which is meant to prevent accidents
due to simultaneous accesses from different threads. That does not always
work that great and can lead to some kind of indefinite deadlock situation.
You can
On Wednesday, July 31, 2013 12:35:04 PM UTC-7, Nobu Games wrote:
Just another related thought: SQLiteDatabase contains some implicit
transaction magic under the hood which is meant to prevent accidents
due to simultaneous accesses from different threads. That does not always
work that
On Thursday, August 1, 2013 2:01:29 AM UTC+4, Nathan wrote:
In older Android versions that error was not treated gracefully and the
database file could get corrupted. In newer versions you are greeted with
an exception. When the database file gets corrupted, the default behavior
of
9 matches
Mail list logo
