From 77bbc1c4af087d009fdfa3d7d4c9a720b7cc9c5b Mon Sep 17 00:00:00 2001 From: "Luke \"Jared\" Bennett" Date: Thu, 4 May 2017 10:47:44 +0100 Subject: Reset schema and migration --- ...dd_clientside_sentry_to_application_settings.rb | 65 ++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb diff --git a/db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb b/db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb new file mode 100644 index 00000000000..9462d858334 --- /dev/null +++ b/db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb @@ -0,0 +1,65 @@ +# See http://doc.gitlab.com/ce/development/migration_style_guide.html +# for more information on how to write migrations for GitLab. + +class AddClientsideSentryToApplicationSettings < ActiveRecord::Migration + include Gitlab::Database::MigrationHelpers + + # Set this constant to true if this migration requires downtime. + DOWNTIME = false + + # When a migration requires downtime you **must** uncomment the following + # constant and define a short and easy to understand explanation as to why the + # migration requires downtime. + # DOWNTIME_REASON = '' + + # When using the methods "add_concurrent_index", "remove_concurrent_index" or + # "add_column_with_default" you must disable the use of transactions + # as these methods can not run in an existing transaction. + # When using "add_concurrent_index" or "remove_concurrent_index" methods make sure + # that either of them is the _only_ method called in the migration, + # any other changes should go in a separate migration. + # This ensures that upon failure _only_ the index creation or removing fails + # and can be retried or reverted easily. + # + # To disable transactions uncomment the following line and remove these + # comments: + disable_ddl_transaction! + + # Reversability was tested when I made an update the originally irreversible + # migration after I ran it, so I could test that the down method worked and then + # the up method worked. + + def up + add_column_with_default :application_settings, :clientside_sentry_enabled, :boolean, default: false + add_column :application_settings, :clientside_sentry_dsn, :string + end + + def down + remove_columns :application_settings, :clientside_sentry_enabled, :clientside_sentry_dsn + end +end + +class AddClientsideSentryToApplicationSettings < ActiveRecord::Migration + include Gitlab::Database::MigrationHelpers + + # Set this constant to true if this migration requires downtime. + DOWNTIME = false + + # When a migration requires downtime you **must** uncomment the following + # constant and define a short and easy to understand explanation as to why the + # migration requires downtime. + # DOWNTIME_REASON = '' + + # When using the methods "add_concurrent_index" or "add_column_with_default" + # you must disable the use of transactions as these methods can not run in an + # existing transaction. When using "add_concurrent_index" make sure that this + # method is the _only_ method called in the migration, any other changes + # should go in a separate migration. This ensures that upon failure _only_ the + # index creation fails and can be retried or reverted easily. + # + # To disable transactions uncomment the following line and remove these + # comments: + disable_ddl_transaction! + + +end -- cgit v1.2.1