I tend to abstract at a higher level since some se...
# squarelibraries
j
I tend to abstract at a higher level since some semantic operation from the UI might want to execute multiple queries
k
I'm intending to wrap all of this in a repository with a retrofit API. But I think this answers my questions.
that being said, is there any plan on marking queries as suspend from the codegen? Something like
Copy code
suspend selectByNames:
SELECT *
FROM hockeyPlayer
WHERE full_name IN ?;
I don't know how this would affect other areas, like transactions for example
j
we tend to prefer reactive selects so that updates are pushed
for mutator queries it does get complicated with transactions if you have suspend functions
k
I guess I should have specified tSQL instead. Bad example.
I'm aware of
Flow
for queries which i think is neat