Use CockroachDB-compatible DROP INDEX CASCADE syntax

FixInitializerService
Ya
24 Aprili 2026, 23:24 UTC
Mwandishi
Kamo
Ahadi ya
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.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei