has_many_attached
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3
- 2.1.0
- 2.2.1
- 2.3.8
- 3.0.0
- 3.0.9
- 3.1.0
- 3.2.1
- 3.2.8
- 3.2.13
- 4.0.2
- 4.1.8
- 4.2.1
- 4.2.7
- 4.2.9
- 5.0.0.1
- 5.1.7
- 5.2.3
- 6.0.0 (0)
- 6.1.3.1 (25)
- 6.1.7.7 (0)
- 7.0.0 (0)
- 7.1.3.2 (0)
- 7.1.3.4 (0)
- 7.2.3 (38)
- 8.0.0 (0)
- 8.1.1 (0)
- What's this?
has_many_attached(name, dependent: :purge_later, service: nil, strict_loading: false)
public
Specifies the relation between multiple attachments and the model.
class Gallery < ApplicationRecord has_many_attached :photos end
There are no columns defined on the model side, Active Storage takes care of the mapping between your records and the attachments.
Under the covers, this relationship is implemented as a has_many association to a ActiveStorage::Attachment record and a has_many-through association to a ActiveStorage::Blob record. These associations are available as photos_attachments and photos_blobs. But you shouldn’t need to work with these associations directly in most circumstances.
Instead, has_many_attached generates an ActiveStorage::Attached::Many proxy to provide access to the associations and factory methods, like attach:
user.photos.attach(uploaded_file)
The :dependent option defaults to :purge_later. This means the attachments will be purged (i.e. destroyed) in the background whenever the record is destroyed. If an ActiveJob::Backend queue adapter is not set in the application set it to purge instead.
If you need the attachment to use a service which differs from the globally configured one, pass the :service option. For example:
class Gallery < ActiveRecord::Base has_many_attached :photos, service: :s3 end
:service can also be specified as a proc, and it will be called with the model instance:
class Gallery < ActiveRecord::Base has_many_attached :photos, service: ->(gallery) { gallery.personal? ? :personal_s3 : :s3 } end
To avoid N+1 queries, you can include the attached blobs in your query like so:
Gallery.where(user: Current.user).with_attached_photos
If you need to enable strict_loading to prevent lazy loading of attachments, pass the :strict_loading option. You can do:
class Gallery < ApplicationRecord has_many_attached :photos, strict_loading: true end
Note: Active Storage relies on polymorphic associations, which in turn store class names in the database. When renaming classes that use has_many, make sure to also update the class names in the active_storage_attachments.record_type polymorphic type column of the corresponding rows.

