about summary refs log tree commit diff
path: root/db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb
diff options
context:
space:
mode:
authorDavid Yip <yipdw@member.fsf.org>2017-10-21 14:47:17 -0500
committerDavid Yip <yipdw@member.fsf.org>2017-10-21 14:54:36 -0500
commit670e6a33f8eeca628707dc020e02ce32502d74a4 (patch)
tree527043ee2b85d5a18dc5c51acd7277fc560b3e78 /db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb
parentcd04e3df58c09b0faca81ccc820b2cd5e12c2890 (diff)
Move KeywordMute into Glitch namespace.
There are two motivations for this:

1. It looks like we're going to add other features that require
   server-side storage (e.g. user notes).

2. Namespacing glitchsoc modifications is a good idea anyway: even if we
   do not end up doing (1), if upstream introduces a keyword-mute feature
   that also uses a "KeywordMute" model, we can avoid some merge
   conflicts this way and work on the more interesting task of
   choosing which implementation to use.
Diffstat (limited to 'db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb')
-rw-r--r--db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb7
1 files changed, 7 insertions, 0 deletions
diff --git a/db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb b/db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb
new file mode 100644
index 000000000..269bb49d6
--- /dev/null
+++ b/db/migrate/20171021191900_move_keyword_mutes_into_glitch_namespace.rb
@@ -0,0 +1,7 @@
+class MoveKeywordMutesIntoGlitchNamespace < ActiveRecord::Migration[5.1]
+  def change
+    safety_assured do
+      rename_table :keyword_mutes, :glitch_keyword_mutes
+    end
+  end
+end