Skip to content

Update user type migration finalization method

Pavel Shutsin requested to merge 386474-make-user-user_type-not-nullable-part-4-followup into master

What does this MR do and why?

Follow-up to fix finalization method. See !121516 (comment 1446316738) for details.

be rake db:migrate:down:main VERSION=20230523101514
main: == [advisory_lock_connection] object_id: 223560, pg_backend_pid: 29336
main: == 20230523101514 FinalizeUserTypeMigration: reverting ========================
main: == 20230523101514 FinalizeUserTypeMigration: reverted (0.0054s) ===============

be rake db:migrate
main: == [advisory_lock_connection] object_id: 223940, pg_backend_pid: 49288
main: == 20230523101514 FinalizeUserTypeMigration: migrating ========================
main: -- transaction_open?()
main:    -> 0.0000s
main: == 20230523101514 FinalizeUserTypeMigration: migrated (0.0512s) ===============

main: == [advisory_lock_connection] object_id: 223940, pg_backend_pid: 49288

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #386474 (closed)

Edited by Diogo Frazão

Merge request reports