amar_1995
07/12/2020, 7:45 AMnglauber
07/12/2020, 3:15 PMyourLiveData._observeAsState_()amar_1995
07/12/2020, 3:25 PMamar_1995
07/12/2020, 3:25 PMTimo Drick
07/12/2020, 5:43 PMamar_1995
07/13/2020, 3:26 AMNot in frame error on any element updated.amar_1995
07/13/2020, 9:40 AMmolikto
07/13/2020, 10:00 AMLIMIT , so you don't load too much data into memory? and you have two query one for first page and then one for load more? maybe you can use @Query and combine with InvalidationTracker.Observer API instead, then create your own Observable .molikto
07/13/2020, 10:02 AMamar_1995
07/13/2020, 10:13 AMLIMIT and getting the list of data as livedata from room query.amar_1995
07/13/2020, 10:15 AMamar_1995
07/13/2020, 10:16 AMamar_1995
07/13/2020, 10:17 AMmolikto
07/13/2020, 10:22 AM@LiveData is not a useful abstraction, because the query doesn't conrespond to a list of items that can be directly shown to users. it is better to use the two query as one-off @Query , and construct your own LiveData insteadamar_1995
07/13/2020, 10:51 AM@Query and then construct my own LiveData of that list ?amar_1995
07/13/2020, 10:53 AMmolikto
07/13/2020, 10:59 AMamar_1995
07/13/2020, 11:42 AMamar_1995
07/14/2020, 1:19 AMInvalidationTracker.Observer . Due you have any example. It will be a great help