You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would just like some clarity on this. The user guide states that UUID fields should be used for model relationships, and that Services should control the relationship between models.
If a relationship spans multiple tables, say: Book -> Author -> Organisation -> Address, does this mean we would need to execute 4 SELECT queries (through different APIs) if we want a Book's Address, aggregating the results similar to Django's prefetch functionality?
Thanks!
The text was updated successfully, but these errors were encountered:
If you have four separate domains and you have that requirement, then yes?
But what if you have that data structure normally with foreign keys and you're doing joins?
That also seems a bit obtuse.
I wonder if there is a more optimal way - creating a BookWithAddress that stores the values together so you're not doing expensive queries all the time, perhaps?
I would just like some clarity on this. The user guide states that UUID fields should be used for model relationships, and that Services should control the relationship between models.
If a relationship spans multiple tables, say:
Book
->Author
->Organisation
->Address
, does this mean we would need to execute 4 SELECT queries (through different APIs) if we want aBook
'sAddress
, aggregating the results similar to Django's prefetch functionality?Thanks!
The text was updated successfully, but these errors were encountered: