mastodon/db/post_migrate/20180813160548_post_migrate...

# frozen_string_literal: true

class PostMigrateFilters < ActiveRecord::Migration[5.2]
  disable_ddl_transaction!

  def up
    drop_table :glitch_keyword_mutes if table_exists? :glitch_keyword_mutes
  end

  def down; end
end
Fix most rubocop issues (#2165) * Run rubocop --autocorrect on app/, config/ and lib/, also manually fix some remaining style issues * Run rubocop --autocorrect-all on db/ * Run rubocop --autocorrect-all on `spec/` and fix remaining issues 2023-04-09 04:25:30 -05:00			`# frozen_string_literal: true`

Split custom filter migration script using the post-deployment migration system There were some concerns with the custom filter migration script dropping a table, thus making it unsafe to run in a zero-downtime setting. Upstream introduced a way to run migrations after deployment, so revisit the old migration script to make use of this. 2018-08-13 11:17:48 -05:00			`class PostMigrateFilters < ActiveRecord::Migration[5.2]`
			`disable_ddl_transaction!`

			`def up`
			`drop_table :glitch_keyword_mutes if table_exists? :glitch_keyword_mutes`
			`end`

Fix most rubocop issues (#2165) * Run rubocop --autocorrect on app/, config/ and lib/, also manually fix some remaining style issues * Run rubocop --autocorrect-all on db/ * Run rubocop --autocorrect-all on `spec/` and fix remaining issues 2023-04-09 04:25:30 -05:00			`def down; end`
Split custom filter migration script using the post-deployment migration system There were some concerns with the custom filter migration script dropping a table, thus making it unsafe to run in a zero-downtime setting. Upstream introduced a way to run migrations after deployment, so revisit the old migration script to make use of this. 2018-08-13 11:17:48 -05:00			`end`