"Bug" with Ash.Seed.upsert on attribute multitenancy with identities.
I have an identity defined as:
identity :unique_name [:name] on an attribute multitenant app. The migration is well generated and creates a unique_index on [:tenant_id, :name]. But when using upsert on Seed, when I specify identity: :unique_name it does not include the tenant_id which fails with error ERROR 42P10 (invalid_column_reference) there is no unique or exclusion constraint matching the ON CONFLICT specification.
The current fix is to change my identity to identity :unique_name [:tenant_id, :name]. Is this what should be expected when difining unique_indexes in multi-tenant apps?0 Replies