Fixed
Status Update
No update yet.
Comments
mm...@commonsware.com
Thanks for the thorough report - you're right about the problem, and the workaround looks good - it even handles the fast cases for initialization and setList(null) nicely.
Fix and tests submitted internally, should go out with next paging release.
Fix and tests submitted internally, should go out with next paging release.
yb...@google.com
yb...@google.com
ya...@google.com
Actually, I'd like to know more about what failed here and why.
I'm curious if InstantTaskExecutorRule is putting paging into an unexpected state - do you have a sample project that reproduces the issue?
When hitting this outside of a test, are you specifying any custom executors, possibly ones which run main thread tasks immediately instead of posting them?
I'm curious if InstantTaskExecutorRule is putting paging into an unexpected state - do you have a sample project that reproduces the issue?
When hitting this outside of a test, are you specifying any custom executors, possibly ones which run main thread tasks immediately instead of posting them?
bo...@gmail.com
I don't have a sample project that hits this.
The problem does not happen very often outside of the test scripts, but we are not running any custom executors. The PagedListAdapter gets the data through a LivePagedListProvider from room db.
The problem does not happen very often outside of the test scripts, but we are not running any custom executors. The PagedListAdapter gets the data through a LivePagedListProvider from room db.
ya...@google.com
This specific issue should be fixed with the Paging Alpha 4 that just released.
Filedhttps://issuetracker.google.com/issues/70351983 to track testing around InstantTaskExecutorRule.
Filed
ma...@liulishuo.com
Then if I migrate from a database version which uses lower version of Room, I need to write large numbers of modify column to NOT NULL s ?
Description
Version used: 1.0.0-alpha1
Devices/Android versions reproduced on: Android Studio 3.0 Canary 1
There doesn't appear to be a way to add general SQLite column constraints [1] to the generated schema. In particular, my application uses NOT NULL and COLLATE NOCASE on some columns and I would like to be able to have Room generate entities with those clauses.
From what I can see there isn't any "escape hatch" to manually adjust the generated schema to workaround this issue.
1: