Support for ManyToMany, ManyToOne, OneToMany
Closed this issue · 1 comments
It is possible to support classic relational ManyToMany, ManyToOne, OneToMany by adding event subscribers which handle this before flushing entities. How about taking this into the lib by extending with doctrine annotations and instead of event subscribers, check for these relations right before flushing.
Advantage: You do not have to write your own subscriber. Although there are possibilities like nested documents etc. there are some cases where you definitely need classical relational relationships and you need some mechanism to update everything automatically instead of doing it all yourself. Like the usual doctrine behaviour.
Since the database doesn't really support relations other than parent/child i think it is not easy or appropriate to try and map relational db concepts into the core system just because the other ORMs offer them. Also consider that there are many cases to handle with complexity of shards, indexes, types, mappings and so on so it is probably a big challenge to create a relational mapping that is robust.
Personally i think the flexibility of the library is paramount and typically relationships are often designed uniquely to specific applications. If you want to reduce code duplication, you can combine several relationship handling functions into a single subscriber and abstract at the application code level.
Having said that if you have an idea you can sketch out that is generally applicable and safe for use in a lucene db context then i'd be happy to review!