discourse/spec/fixtures/db/migrate/rename_column/20990309014014_rename_colum...

# frozen_string_literal: true

class RenameColumn < ActiveRecord::Migration[5.1]
  def up
    rename_column :users, :username, :username1
  end

  def down
    raise "not tested"
  end
end
DEV: use #frozen_string_literal: true on all spec This change both speeds up specs (less strings to allocate) and helps catch cases where methods in Discourse are mutating inputs. Overall we will be migrating everything to use #frozen_string_literal: true it will take a while, but this is the first and safest move in this direction 2019-04-29 20:27:42 -04:00			`# frozen_string_literal: true`

FEATURE: protect against accidental column or table drops Often we need to amend our schema, it is tempting to use drop_table, rename_column and drop_column to amned schema trouble though is that existing code that is running in production can depend on the existance of previous schema leading to application breaking until new code base is deployed. The commit enforces new rules to ensure we can never drop tables or columns in migrations and instead use Migration::ColumnDropper and Migration::TableDropper to defer drop the db objects 2018-03-20 03:20:50 -04:00			`class RenameColumn < ActiveRecord::Migration[5.1]`
			`def up`
			`rename_column :users, :username, :username1`
			`end`

			`def down`
			`raise "not tested"`
			`end`
			`end`