Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

fix: make drop_uniqueness_constraint_on_phone idempotent #1817

Merged
merged 1 commit into from
Oct 28, 2024
Merged

fix: make drop_uniqueness_constraint_on_phone idempotent #1817

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions migrations/20240806073726_drop_uniqueness_constraint_on_phone.up.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,16 @@
alter table {{ index .Options "Namespace" }}.mfa_factors drop constraint if exists mfa_factors_phone_key;
do $$
begin
-- if both indexes exist, it means that the schema_migrations table was truncated and the migrations had to be rerun
if (
select count(*) = 2
from pg_indexes
where indexname in ('unique_verified_phone_factor', 'unique_phone_factor_per_user')
and schemaname = '{{ index .Options "Namespace" }}'
) then
execute 'drop index {{ index .Options "Namespace" }}.unique_verified_phone_factor';
end if;

if exists (
select 1
from pg_indexes
Expand Down
Loading