it depends on what you're using the data for. SQLD...
# squarelibraries
a
it depends on what you're using the data for. SQLDelight is purposely trying to incentivize not doing SELECT * everywhere and especially not SELECT * FROM x JOIN y If you really need all the columns from both tables for every single row, then definitely do a single query. If you're just trying to get table types back from sqldelight ( 😞 ) then use 2 separate queries
d
I guess what I really wanted to ask is it possible that sqlDelight will be so clever to create an inner
List<>
for me (be it
*
or selected columns). Currently this task of mapping one-to-many falls on my shoulders, wouldn't it be possible to auto-generate a data class which models this relation. Or are there some drawbacks?