8469f59d78
This backports all EE schema changes to CE, including EE migrations, ensuring both use the same schema. == Updated tests A spec related to ghost and support bot users had to be modified to make it pass. The spec in question assumes that the "support_bot" column exists when defining the spec. In the single codebase setup this is not the case, as the column is backported in a later migration. Any attempt to use a different schema version or use of "around" blocks to conditionally disable specs won't help, as reverting the backport migration would also drop the "support_bot" column. Removing the "support_bot" tests entirely appears to be the only solution. We also need to update some foreign key tests now that we have backported the EE columns. Fortunately, these changes are very minor. == Backporting migrations This commit moves EE specific migrations (except those for the Geo tracking database) and related files to CE, and also removes any traces of the ee/db directory. Some migrations had to be modified or removed, as they no longer work with the schema being backported. These migrations were all quite old, so we opted for removing them where modifying them would take too much time and effort. Some old migrations were modified in EE, while also existing in CE. In these cases we took the EE code, and in one case removed them entirely. It's not worth spending time trying to merge these changes somehow as we plan to remove old migrations around the release of 12.0, see https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
28 lines
1.1 KiB
Ruby
28 lines
1.1 KiB
Ruby
|
|
class CreateUserActivities < ActiveRecord::Migration[4.2]
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = true
|
|
|
|
# When a migration requires downtime you **must** uncomment the following
|
|
# constant and define a short and easy to understand explanation as to why the
|
|
# migration requires downtime.
|
|
DOWNTIME_REASON = 'Adding foreign key'.freeze
|
|
|
|
# When using the methods "add_concurrent_index" or "add_column_with_default"
|
|
# you must disable the use of transactions as these methods can not run in an
|
|
# existing transaction. When using "add_concurrent_index" make sure that this
|
|
# method is the _only_ method called in the migration, any other changes
|
|
# should go in a separate migration. This ensures that upon failure _only_ the
|
|
# index creation fails and can be retried or reverted easily.
|
|
#
|
|
# To disable transactions uncomment the following line and remove these
|
|
# comments:
|
|
# disable_ddl_transaction!
|
|
|
|
def change
|
|
create_table :user_activities do |t|
|
|
t.belongs_to :user, index: { unique: true }, foreign_key: { on_delete: :cascade }
|
|
t.datetime :last_activity_at, null: false
|
|
end
|
|
end
|
|
end
|