Building a Shopping List App: Jetpack Compose and Room Database-Repository

[@ubersticks]

Question: I have seen two ways to handle multiple tables in Room... this way where you create @Query() using SQL JOIN statements, and another where you create @Entities for "compound" data sets that consist of portions of multiple tables - these entities make use of the Room @Relation to describe the id linkage between the tables. Is there a reason to prefer one or the other?