Fixed
Status Update
Comments
da...@google.com <da...@google.com> #2
there are some image for help
ae...@gmail.com <ae...@gmail.com> #3
hello?
da...@google.com <da...@google.com>
da...@google.com <da...@google.com>
ap...@google.com <ap...@google.com> #4
Project: platform/frameworks/support
Branch: androidx-main
Author: Daniel Santiago Rivera <
Link:
Implicitly invalidation when a writer connection is used
Expand for full commit details
Implicitly invalidation when a writer connection is used
To keep behaviour consistent with existing usage of SupportSQLite via Room, when a write operation is done using the writer connection, Room should attempt to check for invalidation and refresh observers.
Bug: 340606803
Test: BaseQueryTest
Change-Id: I73ef6de36166bd339e388196a4cfd559669a8e66
Files:
- M
room/integration-tests/multiplatformtestapp/src/commonTest/kotlin/androidx/room/integration/multiplatformtestapp/test/BaseQueryTest.kt
- M
room/room-runtime/src/commonMain/kotlin/androidx/room/RoomDatabase.kt
Hash: 86eab0c53ac26323eef091101a22626ae290cacd
Date: Fri Feb 28 10:30:08 2025
Description
In this block :
After wrapped in here , data flow couldn't receive any change, neither any invalidation observer.
immediateTransaction
, which mentionedIn pure Room without KMP, multiple DAO operations normally wrapped in
database.withTransaction
block. How to do in KMP?