0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
16 lines
435 B
Ruby
16 lines
435 B
Ruby
# Convert legacy Markdown-emphasized notes to the current, non-emphasized format
|
|
#
|
|
# _mentioned in 54f7727c850972f0401c1312a7c4a6a380de5666_
|
|
#
|
|
# becomes
|
|
#
|
|
# mentioned in 54f7727c850972f0401c1312a7c4a6a380de5666
|
|
class ConvertLegacyReferenceNotes < ActiveRecord::Migration[4.2]
|
|
def up
|
|
execute %q{UPDATE notes SET note = trim(both '_' from note) WHERE system = true AND note LIKE '\_%\_'}
|
|
end
|
|
|
|
def down
|
|
# noop
|
|
end
|
|
end
|