Room Flowable transaction events












0















I bound my adapter with room-db Flowables



db.myDao().loadByTrackId(tracksId)
.observeOn(AndroidSchedulers.mainThread())
.subscribeOn(Schedulers.io())
.subscribe({ comments ->
Timber.d("setDataAD " + comments.size())
adapter.setData(comments.toMutableList())
}, ...
)


from somewhere I update the Room database



db.myDao().updateComments(pair.first.data, pair.second.data)


dao:



@Transaction
fun updateComments(commentOrigin: List<Comment>, commentNew: List<Comment>) {
delete(commentOrigin)
insertAll(commentNew)
}

@Delete
fun delete(comments: List<Comment>)

@Insert(onConflict = OnConflictStrategy.REPLACE)
fun insertAll(comments: List<Comment>)


When now 3 are deleted and 3 are inserted and with the approach of using a @Transaction I assumed a single event with a Flowable, but I measured a firework of Flowables



setDataAD 0
setDataAD 3
setDataAD 3
setDataAD 0
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 0
setDataAD 3
setDataAD 3
setDataAD 0
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 0
setDataAD 3
setDataAD 0
setDataAD 3
setDataAD 3


How can this solved to get just one single event/Flowable?
Or with other words: how can I prevent some db updates, reflected by Flowables










share|improve this question





























    0















    I bound my adapter with room-db Flowables



    db.myDao().loadByTrackId(tracksId)
    .observeOn(AndroidSchedulers.mainThread())
    .subscribeOn(Schedulers.io())
    .subscribe({ comments ->
    Timber.d("setDataAD " + comments.size())
    adapter.setData(comments.toMutableList())
    }, ...
    )


    from somewhere I update the Room database



    db.myDao().updateComments(pair.first.data, pair.second.data)


    dao:



    @Transaction
    fun updateComments(commentOrigin: List<Comment>, commentNew: List<Comment>) {
    delete(commentOrigin)
    insertAll(commentNew)
    }

    @Delete
    fun delete(comments: List<Comment>)

    @Insert(onConflict = OnConflictStrategy.REPLACE)
    fun insertAll(comments: List<Comment>)


    When now 3 are deleted and 3 are inserted and with the approach of using a @Transaction I assumed a single event with a Flowable, but I measured a firework of Flowables



    setDataAD 0
    setDataAD 3
    setDataAD 3
    setDataAD 0
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 0
    setDataAD 3
    setDataAD 3
    setDataAD 0
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 0
    setDataAD 3
    setDataAD 0
    setDataAD 3
    setDataAD 3


    How can this solved to get just one single event/Flowable?
    Or with other words: how can I prevent some db updates, reflected by Flowables










    share|improve this question



























      0












      0








      0








      I bound my adapter with room-db Flowables



      db.myDao().loadByTrackId(tracksId)
      .observeOn(AndroidSchedulers.mainThread())
      .subscribeOn(Schedulers.io())
      .subscribe({ comments ->
      Timber.d("setDataAD " + comments.size())
      adapter.setData(comments.toMutableList())
      }, ...
      )


      from somewhere I update the Room database



      db.myDao().updateComments(pair.first.data, pair.second.data)


      dao:



      @Transaction
      fun updateComments(commentOrigin: List<Comment>, commentNew: List<Comment>) {
      delete(commentOrigin)
      insertAll(commentNew)
      }

      @Delete
      fun delete(comments: List<Comment>)

      @Insert(onConflict = OnConflictStrategy.REPLACE)
      fun insertAll(comments: List<Comment>)


      When now 3 are deleted and 3 are inserted and with the approach of using a @Transaction I assumed a single event with a Flowable, but I measured a firework of Flowables



      setDataAD 0
      setDataAD 3
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 3


      How can this solved to get just one single event/Flowable?
      Or with other words: how can I prevent some db updates, reflected by Flowables










      share|improve this question
















      I bound my adapter with room-db Flowables



      db.myDao().loadByTrackId(tracksId)
      .observeOn(AndroidSchedulers.mainThread())
      .subscribeOn(Schedulers.io())
      .subscribe({ comments ->
      Timber.d("setDataAD " + comments.size())
      adapter.setData(comments.toMutableList())
      }, ...
      )


      from somewhere I update the Room database



      db.myDao().updateComments(pair.first.data, pair.second.data)


      dao:



      @Transaction
      fun updateComments(commentOrigin: List<Comment>, commentNew: List<Comment>) {
      delete(commentOrigin)
      insertAll(commentNew)
      }

      @Delete
      fun delete(comments: List<Comment>)

      @Insert(onConflict = OnConflictStrategy.REPLACE)
      fun insertAll(comments: List<Comment>)


      When now 3 are deleted and 3 are inserted and with the approach of using a @Transaction I assumed a single event with a Flowable, but I measured a firework of Flowables



      setDataAD 0
      setDataAD 3
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 0
      setDataAD 3
      setDataAD 0
      setDataAD 3
      setDataAD 3


      How can this solved to get just one single event/Flowable?
      Or with other words: how can I prevent some db updates, reflected by Flowables







      kotlin rx-java android-room android-livedata






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 8 '18 at 18:30









      Filip

      3,07921126




      3,07921126










      asked Nov 15 '18 at 7:36









      hannes achhannes ach

      1,3021419




      1,3021419
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53314459%2froom-flowable-transaction-events%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53314459%2froom-flowable-transaction-events%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          Xamarin.form Move up view when keyboard appear

          Post-Redirect-Get with Spring WebFlux and Thymeleaf

          Anylogic : not able to use stopDelay()