This has come up most recently with users asking to use the Project table. Because it has a many-to-many relationship from Collection Object, it is not supported.
A big issue is that this relationship is used infrequently with user-facing tables. Do the programmers have any thoughts on how we can resolve this?
This has come up most recently with users asking to use the Project table. Because it has a
many-to-manyrelationship from Collection Object, it is not supported.unhandled relationship type: many-to-manyprojectsrelationship field throws an error:type object 'CollectionObject' has no attribute 'projects'A big issue is that this relationship is used infrequently with user-facing tables. Do the programmers have any thoughts on how we can resolve this?
Specifically, the backend infrastructure to support many-to-many relationships was implemented in #7643. Particularly, we made sure the internal datamodel and Django ORM was extensible and ready for future work without a database migration.
Also see #7621 (review) for more considerations about adding support during the development process.
#7643 set the ground work for future work and mostly solidified the design, but there is still some work to be done before the feature is complete.
In short, we need to make sure many-to-many support is implemented via the: