gitlab-org--gitlab-foss/db/migrate/20151103134958_create_lfs_objects_projects.rb

# rubocop:disable all
class CreateLfsObjectsProjects < ActiveRecord::Migration[4.2]
  DOWNTIME = false

  def change
    create_table :lfs_objects_projects do |t|
      t.integer :lfs_object_id, null: false
      t.integer :project_id, null: false

      t.timestamps null: true
    end

    add_index :lfs_objects_projects, :project_id
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 08:39:16 -04:00			`# rubocop:disable all`
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 CreateLfsObjectsProjects < ActiveRecord::Migration[4.2]`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 10:15:02 -05:00			`DOWNTIME = false`

Add support for git lfs. 2015-10-12 10:42:14 -04:00			`def change`
			`create_table :lfs_objects_projects do \|t\|`
			`t.integer :lfs_object_id, null: false`
			`t.integer :project_id, null: false`

Add `null: true` to timestamps in migrations that does not define it This is to ensure that migrations will still be consitent when we will upgrade to Rails 5 which default to `null: false` for timestamps columns. Fixes #23666. Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-28 10:45:08 -05:00			`t.timestamps null: true`
Add support for git lfs. 2015-10-12 10:42:14 -04:00			`end`

			`add_index :lfs_objects_projects, :project_id`
			`end`
			`end`