Commit graph

12 commits

Author SHA1 Message Date
Jan Provaznik
0fc9f9d3e7 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-22 13:18:28 +01:00
Lin Jen-Shin
b95da565cd Enable rubocop for db/**/* and ee/db/**/* 2018-07-25 17:47:12 +08: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
Jacob Vosmaer
0b2670f82f Remove unnecessary semicolons
I could not help myself
2015-04-14 15:45:15 +02:00
Jacob Vosmaer
41a1cb88f4 Use different queries for MySQL and Postgres
I could not find a query that worked on both; these two queries look
very similar and seem to do the same thing.
2015-04-14 15:44:19 +02:00
Jacob Vosmaer
afa47eddcc Also ldap_group_links where provider='ldap' 2015-04-13 11:56:35 +02:00
Jacob Vosmaer
8476d171cc Merge branch 'ldap_migration' of dev.gitlab.org:gitlab/gitlabhq into ldap_migration 2015-04-13 11:52:05 +02:00
Jacob Vosmaer
8b4705fea6 Make migration work if LDAP is disabled 2015-04-13 11:50:00 +02:00
Dmitriy Zaporozhets
04f05ac1fb Check for table instead of class 2015-04-13 12:26:14 +03:00
Jacob Vosmaer
f64db1fab9 Try to explain what we are doing 2015-04-13 11:22:31 +02:00
Dmitriy Zaporozhets
896ea2482b
Change migration to SQL
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2015-04-13 11:50:21 +03:00
Valery Sizov
8666f497ff fix ldap identities 2015-04-11 17:56:45 +03:00