litesuits / litesuits/android-lite-orm
statement aborts at 31: [REPLACE INTO Object
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 1802)
W/System.err(17618): at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method)
W/System.err(17618): at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:972)
W/System.err(17618): at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:788)
W/System.err(17618): at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:86)
W/System.err(17618): at com.litesuits.orm.db.assit.SQLStatement.execInsertWithMapping(SQLStatement.java:111)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SQLStatement.java at execInsertWithMapping, then trace the Android SQLite stack shown in the report, including SQLiteStatement.executeInsert. Reproduce the disk I/O error if possible and determine the conditions that trigger code 1802; done means the cause is identified and the insert path no longer aborts under that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, sqlite
- Domain
- database, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100