The changeset does not define a constraint for a custom unique index about ash_postgres HOT 2 CLOSED

🤔 yeah, this is interesting. There is a way to add custom unique indexes to be checked in the changeset. Specifically:

postgres do
  unique_index_names {[:provider, :provider_id], "...name of constraint"}
end

But we could likely derive these for custom constraints. The only thing is that we need to have atoms for the fields instead of strings, and we don't necessarily want to assume that every key provided to a custom index already exists as an atom.

So, to do this automatically we'd need to

1. make custom_indexes take a list of atom for fields instead of strings
2. add those to the list of unique constraint names to check for.

from ash_postgres.

Fixed in: 0598376

from ash_postgres.