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
Basically what we need to do here is, if the relationship points at the primary key of the target, we should not add the multitenancy attribute. This should be relatively easy to do.
Describe the bug
If i create resource with
and have another resource relating to this one, generated migration is wrong.
Fails with error:
To fix i need to add
which creates unique index with tenant (organization_id in this case prefix) so unique index [:organization_id, :id]
Then migrations works fine
Expected behavior
It would add corrcet unique indexes by default for primary fields with multitenancy
Runtime
The text was updated successfully, but these errors were encountered: