Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-04-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-26 | 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-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-05 | 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-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-05 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-11 | Add rake task `db:obsolete_ignored_columns` | Peter Leitzen | |
Show a list of obsolete `ignored_columns` | |||
2019-09-05 | Use stub_rails_env for Rails.env stubbing | Ash McKenzie | |
RailsHelpers.stub_rails_env takes care of stubbing Rails.env | |||
2019-08-25 | Add helper to exactly undo cleanup_concurrent_column_rename | Reuben Pereira | |
- Also add helper to undo rename_column_concurrently. | |||
2019-08-24 | Drop existing trigger before creating new one | Reuben Pereira | |
- When renaming a column concurrently, drop any existing trigger before attempting to create a new one. When running migration specs multiple times (as it happens during local development), the down method of previous migrations are called. If any of the called methods contains a call to rename_column_concurrently, a trigger will be created and not removed. So, the next time a migration spec is run, if the same down method is executed again, it will cause an error when attempting to create the trigger (since it already exists). Dropping the trigger if it already exists will prevent this problem. | |||
2019-07-29 | Further remove code branches by database type | Andreas Brandl | |
We dropped MySQL support and a lot of mysql specific code has been removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608. This comes in from the other direction and removes any `if postgresql?` branches. | |||
2019-07-26 | Merge branch 'frozen_string_spec_lib' into 'master' | Stan Hu | |
Add frozen_string_literal to spec/lib (part 1) See merge request gitlab-org/gitlab-ce!31130 | |||
2019-07-26 | Add frozen_string_literal to spec/lib (part 1) | Thong Kuah | |
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758 | |||
2019-07-25 | Remove code related to object hierarchy in MySQL | Heinrich Lee Yu | |
These are not required because MySQL is not supported anymore | |||
2019-07-24 | Enable tablesample count strategy by default | Andreas Brandl | |
https://gitlab.com/gitlab-org/gitlab-ce/issues/58792 | |||
2019-07-23 | Remove dead MySQL code | Nick Thomas | |
None of this code can be reached any more, so it can all be removed | |||
2019-07-18 | Improves add_timestamps_with_timezone helper | Alex Kalderimis | |
This improves the `add_timestamps_with_timezone` helper by allowing the column names to be configured. This has the advantage that unnecessary columns can be avoided, saving space. A helper for removing the columns is also provided, to be used in the `down` method of migrations. | |||
2019-06-28 | Support jsonb Default Value in add_column_with_default Migration Helper | Jason Goodman | |
2019-06-19 | Remove import columns from projects table | Stan Hu | |
In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21497, we migrated all project import data into a separate table, `project_import_data`. In addition, we also added: ``` ignore_column :import_status, :import_jid, :import_error ``` In https://gitlab.com/gitlab-com/gl-infra/production/issues/908, we observed some of these `import_error` columns consumed megabytes of error backtraces and caused slow loading of projects whenever a `SELECT * from projects` query loaded the row into memory. Since we have long migrated away from these columns, we can now drop these columns entirely. | |||
2019-06-17 | Allow custom names for concurrent foreign keys | Yorick Peterse | |
This is necessary for backporting the EE schema to ensure backported foreign keys use the same key names. | |||
2019-04-05 | Autocorrect with RSpec/ExampleWording cop | Thong Kuah | |
- rewords examples starting with 'should' - rewords examples starting with 'it' Note: I had to manually fixup "onlies" to "only" | |||
2019-03-12 | Fix counting of groups in admin dashboard | Stan Hu | |
1. Ignore tables that use STI in reltuples count strategy. Models that use Rails' single-type inheritance, such as `Group` and `CiService`, need an additional WHERE clause to count the total properly, which isn't supported by the reltuples strategy. For now, we just omit these from the statistics sampling and rely on the other strategies to get this data. 2. Fix tablesample count strategy not counting groups properly. Models such as `Group` needs a WHERE clause to distinguish it from namespaces. We now add in the WHERE clause if STI is in use. Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/7435 | |||
2019-02-27 | Fix misspellings in app/spec executable lines | Takuya Noguchi | |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com> | |||
2018-12-14 | Remove rails 4 support in CI, Gemfiles, bin/ and config/ | Jasper Maes | |
2018-12-06 | Use approximate counts for big tables | Jan Provaznik | |
2018-12-03 | Move strategies in their own files | Andreas Brandl | |
This improves readability quite a bit. | |||
2018-12-03 | Limit some specs to PostgreSQL only. | Andreas Brandl | |