Verified
Status Update
No update yet.
Comments
yb...@google.com
you can observe both of them at the same time or add 2 observers. If you observe both tables, even if one of them changes, you'll still get a notification.
m6...@mschmitt.info
Two observers, as described in the linked issue, leads to glitches in certain scenarios. (If both changes come from a single transaction and need to be handled together)
If I observe both tables with a single observer and get a notification, then I don't know which table change triggered the notification and have to re-query both tables, which could potentially be a costly operation. I can live with that but I find it a bit sub-optimal, especially since the information which table(s) changed is available to the framework.
If I observe both tables with a single observer and get a notification, then I don't know which table change triggered the notification and have to re-query both tables, which could potentially be a costly operation. I can live with that but I find it a bit sub-optimal, especially since the information which table(s) changed is available to the framework.
yb...@google.com
I see. We technically dispatch them at the same time though relying on that would be ugly. The information is not really kept but we can extract it again (InvalidationTracker just uses ids for tables but that is convertible).
Description
Component used: Room
Version used: 1.0.0-alpha1
Devices/Android versions reproduced on: N/A
- Sample project to trigger the issue. N/A
- A screenrecord or screenshots showing the issue (if UI related). N/A