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 have a question regarding pivot tables. Having this database structure as example:
I want to use row_to_invoice and row_to_budget as pivot tables. In both tables row_id is unique, the correct way to define a pivot table in, for example, invoice entity should be:
My question is if there's a way to define the non-owning side as entities and not collections, similar to @OneToOne pattern in the row entity as row_id in both pivot tables is unique:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a question regarding pivot tables. Having this database structure as example:
I want to use
row_to_invoice
androw_to_budget
as pivot tables. In both tablesrow_id
is unique, the correct way to define a pivot table in, for example,invoice
entity should be:My question is if there's a way to define the non-owning side as entities and not collections, similar to
@OneToOne
pattern in therow
entity asrow_id
in both pivot tables is unique:Beta Was this translation helpful? Give feedback.
All reactions