Commit graph

8 commits

Author SHA1 Message Date
Yorick Peterse
235b105c91
Finish migration to the new events setup
This finishes the procedure for migrating events from the old format
into the new format. Code no longer uses the old setup and the database
tables used during the migration process are swapped, with the old table
being dropped.

While the database migration can be reversed this will 1) take a lot of
time as data has to be coped around 2) won't restore data in the
"events.data" column as we have no way of restoring this.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
2017-09-06 16:40:31 +02:00
Sean McGivern
98bb435f42 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 16:05:25 +01:00
Tomasz Maczukin
b76bfe35c7 Add limit change for 'data' column in 'events' when using MySQL 2016-01-18 21:27:56 +01:00
Stan Hu
e39fdc1ddd Ensure MySQL CI limits DB migrations occur after the fields have been created
Closes https://github.com/gitlabhq/gitlabhq/issues/9753
2015-10-21 00:11:06 -07:00
Dmitriy Zaporozhets
81f9ee48b1 Fix mysql migration 2015-09-09 16:08:09 +02:00
Douwe Maan
046b283127 Groundwork for merging CI into CE 2015-08-25 18:42:46 -07:00
Jacob Vosmaer
cd61239540 Move the adapter check to the migration 2014-04-23 11:08:51 +02:00
Jacob Vosmaer
43e77099d8 Adjust MySQL limits for existing installations 2014-04-23 11:07:36 +02:00