gitlab-org--gitlab-foss/db/migrate/20170206115204_add_column_ghost_to_users.rb

class AddColumnGhostToUsers < ActiveRecord::Migration[4.2]
  DOWNTIME = false

  def up
    add_column :users, :ghost, :boolean
  end

  def down
    remove_column :users, :ghost
  end
end
Add version 4.2 to all existing migrations 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 2018-11-13 02:27:31 -05:00			`class AddColumnGhostToUsers < ActiveRecord::Migration[4.2]`
Use a `ghost` boolean to track ghost users. Rather than using a separate `ghost` state. This lets us have the benefits of both ghost and blocked users (ghost: true, state: blocked) without having to rewrite a number of queries to include cases for `state: ghost`. 2017-02-06 07:07:05 -05:00			`DOWNTIME = false`

			`def up`
Remove the default value for the `users.ghost` database column. The default (false) is not strictly required, and this lets us avoid a potentially expensive migration 2017-02-07 01:43:24 -05:00			`add_column :users, :ghost, :boolean`
Use a `ghost` boolean to track ghost users. Rather than using a separate `ghost` state. This lets us have the benefits of both ghost and blocked users (ghost: true, state: blocked) without having to rewrite a number of queries to include cases for `state: ghost`. 2017-02-06 07:07:05 -05:00			`end`

			`def down`
			`remove_column :users, :ghost`
			`end`
			`end`