BigW Consortium Gitlab
Revert "Optimistic locking for Issue and Merge Requests" The migration to add `lock_version` in !5146 to every issue and merge request takes too long on GitLab.com since it has to add a default value of 0 to every row. Unfortunately, Rails 4.2 doesn't work properly if the value is left as `nil`; anything using optimistic locking cannot be edited. This bug was fixed in Rails 5.0 via this commit: https://github.com/rails/rails/commit/13772bfa49325a8dc26410d2dcb555665a320f92. I suggest we revert this change for now, and when we upgrade to Rails 5.0 we can reintroduce this feature. See merge request !5245
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
_filter.html.haml | Loading commit data... | |
_form.html.haml | Loading commit data... | |
_label_dropdown.html.haml | Loading commit data... | |
_label_page_create.html.haml | Loading commit data... | |
_label_page_default.html.haml | Loading commit data... | |
_milestone_dropdown.html.haml | Loading commit data... | |
_nav.html.haml | Loading commit data... | |
_participants.html.haml | Loading commit data... | |
_search_form.html.haml | Loading commit data... | |
_sidebar.html.haml | Loading commit data... |