- 19 Jan, 2017 1 commit
-
-
Douwe Maan authored
Refactor cycle analytics stages (1st iteration) See merge request !7647
-
- 17 Nov, 2016 3 commits
-
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
- 21 Sep, 2016 1 commit
-
-
Timothy Andrew authored
- Pluralize summary titles - Remove the `run_query` method - always return sql strings from the `date_time_sql` methods
-
- 20 Sep, 2016 5 commits
-
-
Timothy Andrew authored
-
Timothy Andrew authored
- Don't use `TableReferences` - using `.arel_table` is shorter! - Move some database-related code to `Gitlab::Database` - Remove the `MergeRequest#issues_closed` and `Issue#closed_by_merge_requests` associations. They were either shadowing or were too similar to existing methods. They are not being used anywhere, so it's better to remove them to reduce confusion. - Use Rails 3-style validations - Index for `MergeRequest::Metrics#first_deployed_to_production_at` - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that need it. - Other minor refactorings.
-
Timothy Andrew authored
And `scss_lint`
-
Timothy Andrew authored
- Move things common to `Issue` and `MergeRequest` into `Issuable` - Move more database-specific functions into `Gitlab::Database` - Indentation changes and other minor refactorings.
-
Timothy Andrew authored
1. Change multiple updates to a single `update_all` 2. Use cascading deletes 3. Extract an average function for the database median. 4. Move database median to `lib/gitlab/database` 5. Use `delete_all` instead of `destroy_all` 6. Minor refactoring
-
- 16 Sep, 2016 1 commit
-
-
Drew Blessing authored
-
- 15 Jul, 2016 2 commits
- 17 Jun, 2016 1 commit
-
-
Yorick Peterse authored
This changes update_column_in_batches to ensure it always updates all rows now. These changes also allow for an extra SELECT query to be removed, nor does it use the row count for determining offsets and the likes; instead it's only used to determine the batch size.
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 15 Jun, 2016 2 commits
-
-
Yorick Peterse authored
This ensures that whatever locks are acquired aren't held onto until the end of the transaction (= after _all_ rows have been updated). Timing wise there's also no difference between using a transaction and not using one.
-
Yorick Peterse authored
By passing a block to update_column_in_batches() one can now customize the queries executed. This in turn can be used to only update a specific set of rows instead of simply all the rows in the table.
-
- 13 Jun, 2016 3 commits
-
-
Yorick Peterse authored
-
Yorick Peterse authored
Instead of updating a fixed number of rows (based on the amount of rows available at the start of the update) the method "update_column_in_batches" will now continue updating rows until it runs out of rows to process. For a table with a high rate of inserts this may result in the migration taking quite some time. However, the alternative is not all rows being updated or the "change_column_null" method raising an error due to there being NULL values.
-
Yorick Peterse authored
This ensures that whenever changing the NULL constraint of a column fails we still drop the column.
-
- 06 Jun, 2016 1 commit
-
-
Felipe Artur authored
-
- 03 Jun, 2016 3 commits
-
-
Felipe Artur authored
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 22 May, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 19 May, 2016 2 commits
-
-
Yorick Peterse authored
-
Yorick Peterse authored
-
- 12 May, 2016 3 commits
-
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Yorick Peterse authored
These helpers can be used to perform migrations without taking down the entire application. For example, the method "add_column_with_default" can be used to add a new column with a default value without locking the entire table.
-