discourse/db/migrate/20130903154323_allow_null_user_id_on_posts.rb

# frozen_string_literal: true

class AllowNullUserIdOnPosts < ActiveRecord::Migration[4.2]
  def up
    change_column :posts, :user_id, :integer, null: true
    execute "UPDATE posts SET user_id = NULL WHERE nuked_user = true"
    remove_column :posts, :nuked_user
  end

  def down
    add_column :posts, :nuked_user, :boolean, default: false
    change_column :posts, :user_id, :integer, null: false
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-03 08:17:27 +10:00			`# frozen_string_literal: true`

Fix all the errors to get our tests green on Rails 5.1. 2017-08-31 12:06:56 +08:00			`class AllowNullUserIdOnPosts < ActiveRecord::Migration[4.2]`
Change the way nuked users' posts are handled. Allow null in the user_id column of posts. Show these posts in the posts stream. 2013-09-03 17:19:29 -04:00			`def up`
			`change_column :posts, :user_id, :integer, null: true`
			`execute "UPDATE posts SET user_id = NULL WHERE nuked_user = true"`
			`remove_column :posts, :nuked_user`
			`end`

			`def down`
			`add_column :posts, :nuked_user, :boolean, default: false`
			`change_column :posts, :user_id, :integer, null: false`
			`end`
			`end`