summaryrefslogtreecommitdiff
path: root/app/models/internal_id.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-051-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-281-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-151-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-201-0/+10
|
* Always use internal ID tables in development and productionsh-disable-internal-ids-available-checkStan Hu2019-04-221-2/+6
| | | | | | | | | | | To avoid quiet failures that cause consistency errors in the database, we should now assume that the internal_ids table is available since we've had this table for close to a year. For tests that have migrations, we make this check thread-safe via SafeRequestStore. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60718
* Rewind IID on Ci::Pipelinesrewind-iid-on-pipelinesKamil Trzciński2019-04-161-12/+35
| | | | | | | If no pipeline is created we currently have IID gap. This is due to fact that we generate IID not on save, but rather ahead of time. This results, us, losing IIDs.
* Inherit from ApplicationRecord instead of ActiveRecord::BaseNick Thomas2019-03-281-1/+1
|
* Flush InternalId records after importAndreas Brandl2019-01-291-0/+11
| | | | | | | | | | | | | | After the import has finished, we flush (delete) the InternalId records related to the project at hand. This means we're starting over with tracking correct internal id values, a new record will be created automatically when the next internal id is generated. The GitHub importer assigns iid values by using supplied values from GitHub. We skip tracking internal id values during the import in favor of higher concurrency. Deleting any InternalId records after the import has finished is an extra measure to guarantee consistency. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54270.
* Revert "Trigger iid logic from GitHub importer for milestones."Andreas Brandl2019-01-291-3/+3
| | | | This reverts commit 358675d09f6ba0fdcc4a089c6d1da6df9ff6d092.
* Trigger iid logic from GitHub importer for milestones.Andreas Brandl2018-08-161-3/+3
|
* Merge branch 'frozen-string-enable-app-models' into 'master'Rémy Coutable2018-08-021-0/+2
|\ | | | | | | | | Enable frozen string in app/models/*.rb See merge request gitlab-org/gitlab-ce!20851
| * Enable frozen string in app/models/*.rbrepo-forks/gitlab-ce-frozen-string-enable-app-modelsgfyoung2018-07-261-0/+2
| | | | | | | | Partially addresses #47424.
* | Resolve "Allow issue's Internal ID (`iid`) to be set when creating via the API"Jamie Schembri2018-08-011-1/+35
|/
* Merge branch 'master' into per-project-pipeline-iidShinya Maeda2018-05-301-20/+4
|\
| * Remove double-checked internal id generation.Andreas Brandl2018-05-281-20/+4
| | | | | | | | | | | | This was needed for a transition phase only. For details see #45389. Closes #45389.
* | Add per-project pipeline idShinya Maeda2018-05-031-1/+1
|/
* Atomic internal ids for all modelsAndreas Brandl2018-04-201-1/+2
|
* Double-check next value for internal ids.Andreas Brandl2018-04-161-4/+20
| | | | | | | | | | | | | | | | | | This is useful for a transition period to migrate away from `NoninternalAtomicId`. In a situation where both the old and new code to generate a iid value is run at the same time (for example, during a deploy different nodes may serve both versions), this will lead to problems regarding the correct `last_value`. That is, what we track in `InternalId` may get out of sync with the maximum iid present for issues. With this change, we double-check that and correct the `last_value` with the maximum iid found in issues if necessary. This is subject to be removed with the 10.8 release and tracked over here: https://gitlab.com/gitlab-org/gitlab-ce/issues/45389 Closes #45269.
* Address review comments.Andreas Brandl2018-03-161-3/+4
|
* Address review comments.Andreas Brandl2018-03-161-2/+3
|
* Backwards-compat for migration specs.Andreas Brandl2018-03-161-2/+18
| | | | | | The specs are based on a schema version that doesn't know about `internal_ids` table. However, the actual code being execute relies on it.
* Refactor, extract class and improve comments.Andreas Brandl2018-03-161-34/+59
|
* More flexible way of internal id generation.Andreas Brandl2018-03-161-21/+19
|
* Atomic generation of internal ids for issues.Andreas Brandl2018-03-161-0/+84
View Lorry Controller Status