KamoCRM

Use CockroachDB-compatible DROP INDEX CASCADE syntax

FixInitializerService
Shipped
24 ஏப்ரல், 2026 அன்று 11:24 PM UTC
Author
Kamo
Commit
17cf757

CockroachDB rejects ALTER TABLE ... DROP CONSTRAINT for UNIQUE constraints with: unimplemented: cannot drop UNIQUE constraint "uk_org_oauth_provider" using ALTER TABLE DROP CONSTRAINT, use DROP INDEX CASCADE instead Switch the migration to `DROP INDEX IF EXISTS <table>@<index> CASCADE` which CockroachDB accepts. Plain PostgreSQL also accepts the simpler `DROP INDEX IF EXISTS <name> CASCADE` form, so the migration tries both variants for engine portability. Same treatment applied to the legacy uk_voip_provider_config_org_id / **************** safeguards (defensive cleanups in case Hibernate left those constraints behind). Migration is still idempotent and safe to re-run on already-migrated DBs.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing