- 13 Jun, 2017 1 commit
-
-
blackst0ne authored
-
- 29 May, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 28 Apr, 2017 3 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
We're going to add another cop that deals with another aspect of `add_column_with_default`, so we need to separate them.
-
Robert Speicher authored
-
- 05 Apr, 2017 1 commit
-
-
blackst0ne authored
-
- 07 Mar, 2017 1 commit
-
-
Douwe Maan authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 10 Feb, 2017 1 commit
-
-
Yorick Peterse authored
This adds a Rubocop rule to enforce the use of add_concurrent_foreign_key instead of the regular add_foreign_key method. This cop has been disabled for existing migrations so we don't need to change those.
-
- 08 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 29 Jun, 2016 1 commit
-
-
Yorick Peterse authored
There are currently two cops for this: * Migration/AddIndex: checks if indexes are added concurrently * Migration/ColumnWithDefault: checks if columns with default values are added in a concurrent manner Both cops are fairly simple and make no attempt at correcting the code as this is quite hard to do (e.g. modifications may need to be applied in various places in the same file). They however should provide enough to catch people ignoring the comments in generated migrations telling them to use add_concurrent_index or add_column_with_default.
-