Skip to content

Resolve "Remove schema_inconsistencies table"

What does this MR do and why?

In this merge request, we are removing the schema_inconsistencies. We have already removed the model class.

!126299 (merged)

bundle exec rake db:migrate:up:main VERSION=20230802090519
main: == [advisory_lock_connection] object_id: 247100, pg_backend_pid: 25496
main: == 20230802090519 DropSchemaInconsistenciesTable: migrating ===================
main: -- drop_table(:schema_inconsistencies)
main:    -> 0.0018s
main: == 20230802090519 DropSchemaInconsistenciesTable: migrated (0.0055s) ==========
bundle exec rake db:migrate:down:main VERSION=20230802090519
main: == [advisory_lock_connection] object_id: 261000, pg_backend_pid: 24950
main: == 20230802090519 DropSchemaInconsistenciesTable: reverting ===================
main: -- create_table(:schema_inconsistencies)
main: -- quote_column_name(:object_name)
main:    -> 0.0000s
main: -- quote_column_name(:table_name)
main:    -> 0.0000s
main: -- quote_column_name(:valitador_name)
main:    -> 0.0000s
main: -- quote_column_name(:diff)
main:    -> 0.0000s
main:    -> 0.0057s
main: == 20230802090519 DropSchemaInconsistenciesTable: reverted (0.0179s) ==========

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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 #390856 (closed)

Edited by Diogo Frazão

Merge request reports