debian-mirror-gitlab/app/models/concerns/sha_attribute.rb

# frozen_string_literal: true

module ShaAttribute
  extend ActiveSupport::Concern

  class_methods do
    def sha_attribute(name)
      return if ENV['STATIC_VERIFICATION']

      validate_binary_column_exists!(name) if Rails.env.development?

      attribute(name, Gitlab::Database::ShaAttribute.new)
    end

    # This only gets executed in non-production environments as an additional check to ensure
    # the column is the correct type.  In production it should behave like any other attribute.
    # See https://gitlab.com/gitlab-org/gitlab/merge_requests/5502 for more discussion
    def validate_binary_column_exists!(name)
      return unless database_exists?
      return unless table_exists?

      column = columns.find { |c| c.name == name.to_s }

      return unless column

      unless column.type == :binary
        raise ArgumentError, "sha_attribute #{name.inspect} is invalid since the column type is not :binary"
      end
    rescue StandardError => error
      Gitlab::AppLogger.error "ShaAttribute initialization: #{error.message}"
      raise
    end

    def database_exists?
      Gitlab::Database.exists?
    end
  end
end

ShaAttribute::ClassMethods.prepend_mod_with('ShaAttribute')