locomotivecms/engine — Issue #290: Reverse n-to-n
Author: Robsteranium
Created: 2012-01-27 16:31:04+00:00
State: open

Hello,

I need to have an n-to-n relationship between (Project and Client) content types in my app. I gather that mongo obviates the need for a junction table (e.g. project-clients) because a document can have a field storing an array of foreign keys. I understand that the functionality for an N:1 reverse lookup is currently available and I guess that this has provisions for maintaining referential integrity. I'd like to see this expanded to cover the N:N case.

I've started exploring how to do this but I'd appreciate some advice on what I need to consider so that I don't blindly wander down any dead ends. Also, I'm presuming that nobody has already started on this?!

Thanks
Robin