WAI
Status Update
No update yet.
Comments
yb...@google.com
Can you provide the below requested information to better understand the issue:
Can you please test with latest library and update result here.
https://developer.android.com/topic/libraries/support-library/revisions.html
If possible please provide a complete sample application.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Can you please test with latest library and update result here.
If possible please provide a complete sample application.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Description
Version used: 1.0.0-rc1
Devices/Android versions reproduced on: n/a
One of the stated reasons for using @Transaction on an @Query is if the @Query is returning a POJO with a @Relation in it. That way, the cascade retrieval is performed under a transaction.
However, you know at compile time whether the @Query is returning a POJO with a @Relation in it. And, AFAICT, by definition, it is unsafe to use @Query with such a @Relation without a @Transaction. So... why do we need to add the @Transaction annotation? The Room annotation processor ought to have the information necessary to imply @Transaction for an @Query returning a POJO with an @Relation, without @Transaction having to be added manually.