discourse/app/models/backup_metadata.rb

# frozen_string_literal: true

class BackupMetadata < ActiveRecord::Base
  def self.value_for(name)
    where(name: name).pluck_first(:value).presence
  end
end

# == Schema Information
#
# Table name: backup_metadata
#
#  id    :bigint           not null, primary key
#  name  :string           not null
#  value :string
#
FEATURE: Remap uploads during restore when S3 or CDN changes In order for this to work the Backuper stores a couple of site settings in the new backup_metadata table, because the old setting values might not be available on restore anymore. 2019-07-09 13:57:31 +02:00			`# frozen_string_literal: true`

			`class BackupMetadata < ActiveRecord::Base`
			`def self.value_for(name)`
DEV: pluck_first Doing .pluck(:column).first is a very common pattern in Discourse and in most cases, a limit cause isn't being added. Instead of adding a limit clause to all these callsites, this commit adds two new methods to ActiveRecord::Relation: pluck_first, equivalent to limit(1).pluck(*columns).first and pluck_first! which, like other finder methods, raises an exception when no record is found 2019-10-21 11:32:27 +01:00			`where(name: name).pluck_first(:value).presence`
FEATURE: Remap uploads during restore when S3 or CDN changes In order for this to work the Backuper stores a couple of site settings in the new backup_metadata table, because the old setting values might not be available on restore anymore. 2019-07-09 13:57:31 +02:00			`end`
			`end`

			`# == Schema Information`
			`#`
			`# Table name: backup_metadata`
			`#`
			`# id :bigint not null, primary key`
			`# name :string not null`
			`# value :string`
			`#`