Datamapper DataMapper

Comments and changes to this ticket

• 

  Giao Phan December 21st, 2009 @ 07:02 PM

  • no changes were found...

  • links.rb 616 Bytes

• You flagged this item as spam.
  

  Giao Phan January 4th, 2010 @ 02:59 PM

  It looks like links was deprecated at some point. What's the proper way now to pull associated tables in so that you can do things like sorting on that assocation:
  http://www.mail-archive.com/datamapper@googlegroups.com/msg01310.html

• You flagged this item as spam.
  

  Giao Phan January 4th, 2010 @ 05:41 PM

  Ended up working around this by getting the relationship object, and calling inverse on it, and passing that as the link.

• You flagged this item as spam.
  

  Richard Livsey January 16th, 2010 @ 04:02 PM

  Just ran into this issue myself too when upgrading to 0.10.2

• You flagged this item as spam.
  

  DAddYE January 18th, 2010 @ 04:29 AM

  Giao Phan,

  can you put your code for resolve this problem?

• You flagged this item as spam.
  

  DAddYE January 18th, 2010 @ 06:40 AM

  Found!

  Album.all(:links => [Album.relationships[:artist].inverse])
  

  Woww work but it's normal that is so complex?

  Then for ordering (also super iper mega complex)

  Album.all(:order => [DataMapper::Query::Direction.new(Artist.properties[:name])], 
            :links => [Album.relationships[:artist].inverse])
  

  Didn't work... say me that

  ArgumentError - +options[:order]+ entry :name does not map to a property in Album
  

• You flagged this item as spam.
  

  DAddYE January 18th, 2010 @ 08:23 AM

  Mmm, found!

  There is a bug here http://github.com/datamapper/dm-core/blob/master/lib/dm-core/query....

  This:

  when Operator, Direction
              operator = order_entry.operator
   
              unless operator == :asc || operator == :desc
                raise ArgumentError, "+options[:order]+ entry #{inspect} used an invalid operator #{operator}"
              end
   
              assert_valid_order([ order_entry.target ], fields)
  

  Cycle validations only on the current model, but we need to change to order_entry.target!

• You flagged this item as spam.
  

  Johan Kellum March 2nd, 2010 @ 11:29 AM

  • Tag set to “relationships links inverse query”

  This monkey patch will allow you to use the less verbose string/symbol with the :links option.
  It simply adds the inverse. It works for 1-many, many-1 and many-many.
  It's especially useful for a has_many :through
  Ex. User.all(:links => [:roles])

  module DataMapper
    class Query
      def normalize_links
        stack = @links.dup
  
        @links.clear
  
        while link = stack.pop
          relationship = case link
            when Symbol, String             then @relationships[link].inverse
            when Associations::Relationship then link
          end
  
          if relationship.respond_to?(:links)
            stack.concat(relationship.links)
          elsif !@links.include?(relationship)
            repository_name = relationship.relative_target_repository_name
            model           = relationship.target_model
  
            # TODO: see if this can handle extracting the :order option and sort the
            # resulting collection using the order specified by through relationships
  
            model.current_scope.merge(relationship.query).each do |subject, value|
              # TODO: figure out how to merge Query options from links
              if OPTIONS.include?(subject)
                next  # skip for now
              end
  
              # set @repository when appending conditions
              original, @repository = @repository, DataMapper.repository(repository_name)
  
              begin
                append_condition(subject, value, model)
              ensure
                @repository = original
              end
            end
  
            @links << relationship
          end
        end
  
        @links.reverse!
      end
    end
  end