Warn about multiple has_many relationships on one model sharing a predicate, or allow them to produce a solr query that can discriminate on the class_name attribute

[jcoyne]

Formerly HYDRA-875

class Catalog < AF::Base
has_many :releases, :class_name=> "Album", :property=> :is_part_of
has_many :tracks, :class_name=> "Track", :property=> :is_part_of
end

Catalog#releases.send(:construct_query)
produces a query like: is_part_of_s:info:fedora/catalog:7"
which is the same as
Catalog#tracks.send(:construct_query)
=> is_part_of_s:info:fedora/catalog:7"

So Catalog#releases returns the same objects as Catalog#tracks.

[blimey74]

Hi, I think this bug could be affecting some work we're trying to do here at the Royal Library in Copenhagen, is there a workaround or an ETA for the issue?

[jcoyne]

The workaround is to use different predicates (sub-types) for each association. I don't think anyone is working on this right now.

[jcoyne]

@blimey74 I've fixed it in the 6.x branch. Is there another release that you would like it backported to?

[blimey74]

@jcoyne a backport to active-fedora 5.5.0, would be really great, thanks!

[jcoyne]

@blimey74 This patch has been released in active-fedora 5.5.2