We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, My source Postgres 11 db has the following index:
create unique index ix_permission_unique on permissions(tenant_id, name, coalesce(scope_type, ''), coalesce(scope_id, ''));
COALESCE expressions are used to allow NULL only once in nullable columns (Postgres 15 has NULLS NOT DISTINCT option for this)
in destination database kitchen_sync creates index:
create unique index ix_permission_unique on permissions(tenant_id, name);
omitting expressions.
This leads to obvious sync error duplicate key value violates unique constraint "ix_permission_unique".
duplicate key value violates unique constraint "ix_permission_unique"
UPD: destinasion db is Postgres 12. Source is synced to dedicated own db schema in destination db
The text was updated successfully, but these errors were encountered:
Yeah, not implemented yet unfortunately (https://github.com/willbryant/kitchen_sync/blob/main/SCHEMA.md#user-content-schema-things-currently-ignored).
Sorry, something went wrong.
No branches or pull requests
Hello,
My source Postgres 11 db has the following index:
create unique index ix_permission_unique on permissions(tenant_id, name, coalesce(scope_type, ''), coalesce(scope_id, ''));
COALESCE expressions are used to allow NULL only once in nullable columns (Postgres 15 has NULLS NOT DISTINCT option for this)
in destination database kitchen_sync creates index:
create unique index ix_permission_unique on permissions(tenant_id, name);
omitting expressions.
This leads to obvious sync error
duplicate key value violates unique constraint "ix_permission_unique"
.UPD:
destinasion db is Postgres 12. Source is synced to dedicated own db schema in destination db
The text was updated successfully, but these errors were encountered: