Edit Question - KnowledgeHub

Title Body

See comments for updates. I've been struggling to get a clear and straight-forward answer on this one, I'm hoping this time I'll get it! :D I definitely have a lot to learn still with Rails, however I do understand the problem I'm facing and would really appreciate additional help. I have a model called "Task". I have an abstract model called "Target". I would like to relate multiple instances of subclasses of Target to Task. I am not using single table inheritance. I would like to query the polymorphic relationship to return a mixed result set of subclasses of Target. I would like to query individual instances of subclasses of Target to obtain tasks that they are in a relationship with. So, I figure a polymorphic many to many relationship between Tasks and subclasses of Targets is in order. In more detail, I will be able to do things like this in the console (and of course elsewhere): task = Task.find(1) task.targets [...array of all the subclasses of Target here...] But! Assuming models "Store", "Software", "Office", "Vehicle", which are all subclasses of "Target" exist, it would be nice to also traverse the relationship in the other direction: store = Store.find(1) store.tasks [...array of all the Tasks this Store is related to...] software = Software.find(18) software.tasks [...array of all the Tasks this Software is related to...] The database tables implied by polymorphic relationships appears to be capable of doing this traversal, but I see some recurring themes in trying to find an answer which to me defeat the spirit of polymorphic relationships: Using my example still, people appear to want to define Store, Software, Office, Vehicle in Task, which we can tell right away isn't a polymorphic relationship as it only returns one type of model . Similar to the la

Tags (comma-separated) Cancel