While prefixes make almost all tables/indexes/constraints unique, leader_worker_id_unique does not incorporate the prefix. This leads to a conflict when trying to bring up a second instance of Chancy with a different prefix in the same database, as it tries to create an index on its leader table with the same name. I might be misreading the docs, but it seems like the intention of the prefix is to allow multiple applications using Chancy to use the same DB but be otherwise isolated. This schema conflict prevents that.
I'm happy to put up a PR later this week/early next for a migration which renames the constraint to include the prefix if this behavior isn't intentional.
While prefixes make almost all tables/indexes/constraints unique,
leader_worker_id_uniquedoes not incorporate the prefix. This leads to a conflict when trying to bring up a second instance of Chancy with a different prefix in the same database, as it tries to create an index on its leader table with the same name. I might be misreading the docs, but it seems like the intention of the prefix is to allow multiple applications using Chancy to use the same DB but be otherwise isolated. This schema conflict prevents that.I'm happy to put up a PR later this week/early next for a migration which renames the constraint to include the prefix if this behavior isn't intentional.