Question about "sets" for ActiveRecordWrapper #9

Activity

1. tjdett commented on Aug 16, 2012

   

   tjdett

   on Aug 16, 2012

   Contributor

   More actions

   @seandmccarthy I'm looking at this issue right now, as I have I case where records could conceptually belong to more than one set.

   My intention is provide an additional method for defining sets that uses ActiveRecord associations. Something along the lines of:

   class Record < ActiveRecord::Base
     has_many :set_memberships, :class_name => 'RecordSetMembership'
     has_many :sets, :through => :set_memberships
   
     def self.sets
       Set.all
     end
   
   end
   
   class RecordSetMembership < ActiveRecord::Base
     belongs_to :record
     belongs_to :set
   end
   
   class Set < ActiveRecord::Base
     has_many :record_memberships, :class_name => 'RecordSetMembership'
     has_many :records, :through => :record_memberships
   end

   It shouldn't be too hard to check if the results returned by model.sets are ActiveRecord models, use reflection to find the association back to model (eg. set.records) and then use it to perform find.
2. tjdett commented on Aug 16, 2012

   

   tjdett

   on Aug 16, 2012

   Contributor

   More actions

   Pull-request #18 splits out this behaviour into two variants:

   • Model-based sets
   • Attribute-based sets

   In model-based sets, the sets are ActiveRecord models which have an association back to records. They preserve the example DCSet behaviour.

   In attribute-based sets, the set attribute to determine set membership (and the class method simply needs to provide a list of those sets somehow).
3. tjdett

   closed this as completedon Aug 16, 2012