An error occurred fetching the project authors.
- 02 Mar, 2020 1 commit
-
-
GitLab Bot authored
-
- 06 Feb, 2020 1 commit
-
-
GitLab Bot authored
-
- 26 Dec, 2019 1 commit
-
-
GitLab Bot authored
-
- 13 Dec, 2019 1 commit
-
-
GitLab Bot authored
-
- 01 Dec, 2019 1 commit
-
-
GitLab Bot authored
-
- 22 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 04 Oct, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 27 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 18 Sep, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 04 Sep, 2019 1 commit
-
-
Mayra Cabrera authored
Indicate it's the author's responsibility to prepare the merge request for a database review
-
- 27 Aug, 2019 1 commit
-
-
Mayra Cabrera authored
Currently, the DB migrations guide says that "you must" use non-blocking operations (such as CREATE INDEX CONCURRENTLY), always. But this does not make sense in cases of empty tables and leads to splitting the work to multiple non-atomic (with disable_ddl_transaction!) DB migrations. To follow KISS principle, to have fewer DB migrations steps, to have them atomic when it's possible and simplify deployment and troubleshooting, the following exceptions were added to the doc: - index creation, - index dropping, - defining an FK, - adding a column with DEFAULT,
-
- 09 Aug, 2019 1 commit
-
-
Mayra Cabrera authored
- Add a new guideline regarding the file location of background migrations - Add a new section about execution timing guidelines for all different kinds of migrations
-
- 25 Jul, 2019 1 commit
-
-
Andreas Brandl authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65126. Came up in the database office hours call on 2019-07-25.
-
- 19 Jul, 2019 1 commit
-
-