| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-04-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-04-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-04-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-03-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2020-02-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-12-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-12-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-12-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-10-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-10-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-10-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-09-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-09-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-09-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
| 2019-09-04 | Updates the merge request author responsibility | Mayra Cabrera | |
| Indicate it's the author's responsibility to prepare the merge request for a database review | |||
| 2019-08-27 | Migrations guide: use atomic steps, when possible | Mayra Cabrera | |
| 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, | |||
| 2019-08-09 | Adds DB guidelines regarding execution timing | Mayra Cabrera | |
| - 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 | |||
| 2019-07-25 | Add points how to prepare for database reviews | Andreas Brandl | |
| Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65126. Came up in the database office hours call on 2019-07-25. | |||
| 2019-07-19 | Document database review process | Toon Claes | |
| See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069 | |||
Welcome to mirror list, hosted at ThFree Co, Russian Federation.
 |
index : gitlab.com/gitlab-org/gitlab-foss.git | |
| Unnamed repository; edit this file 'description' to name the repository. | root |
| summaryrefslogtreecommitdiff |