Allow more than one relationship between two collections/named relationships #103
Labels
area/collections
Related to the collections system
area/query
Related to the query component
area/schema
Related to the schema system
feature
New feature or request
Currently it is not possible to have two relationships between the same two collections. Should be sorted out soon I think the best alternative would be to create a one-one bridging object between the two, complicating the users' datamodels (much worse than e.g. having to average client-side IMO).
The text was updated successfully, but these errors were encountered: