kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/models/merge_request_diff_commit.rb

33 lines
1.1 KiB
Ruby
Raw Normal View History

Enable frozen string in app/models/*.rb Partially addresses #47424.
2018-07-25 05:30:33 -04:00
# frozen_string_literal: true
Inherit from ApplicationRecord instead of ActiveRecord::Base
2019-03-28 09:17:42 -04:00
class MergeRequestDiffCommit < ApplicationRecord
Add latest changes from gitlab-org/gitlab@master
2020-02-12 16:08:48 -05:00
include BulkInsertSafe
Add table for merge request commits This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
2017-06-16 10:00:58 -04:00
include ShaAttribute
Add latest changes from gitlab-org/gitlab@master
2020-01-29 10:08:59 -05:00
include CachedCommit
Add table for merge request commits This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
2017-06-16 10:00:58 -04:00
belongs_to :merge_request_diff
sha_attribute :sha
alias_attribute :id, :sha
Add latest changes from gitlab-org/gitlab@master
2020-03-04 07:07:52 -05:00
# Deprecated; use `bulk_insert!` from `BulkInsertSafe` mixin instead.
# cf. https://gitlab.com/gitlab-org/gitlab/issues/207989 for progress
Add table for merge request commits This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
2017-06-16 10:00:58 -04:00
def self.create_bulk(merge_request_diff_id, commits)
rows = commits.map.with_index do |commit, index|
# See #parent_ids.
commit_hash = commit.to_hash.except(:parent_ids)
sha = commit_hash.delete(:id)
commit_hash.merge(
merge_request_diff_id: merge_request_diff_id,
relative_order: index,
Add latest changes from gitlab-org/gitlab@master
2020-01-29 10:08:59 -05:00
sha: Gitlab::Database::ShaAttribute.serialize(sha), # rubocop:disable Cop/ActiveRecordSerialize
Handle large values on `MergeRequestDiffCommit` dates
2017-10-30 19:21:56 -04:00
authored_date: Gitlab::Database.sanitize_timestamp(commit_hash[:authored_date]),
committed_date: Gitlab::Database.sanitize_timestamp(commit_hash[:committed_date])
Add table for merge request commits This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
2017-06-16 10:00:58 -04:00
)
end
Gitlab::Database.bulk_insert(self.table_name, rows)
end
end
Copy permalink