Sound a lot like corresponding node references and backreferences

http://en.wikipedia.org/wiki/Sisyphus

In short, I was just trying to see if I could do it. I built the first piece of functionality out myself as an exercise. I plan on scrapping it and integrating the second piece with one of the existing backreference modules... the only problem is that there are so many, and the intermediary node management code is interwoven with the backref code, meaning that it can't be abstracted unless a bunch of existing backref modules implement a robust hooks system or something.

Also, though I can't speak for backreferences, I've investigated CNR in some depth now, and I've noticed that it destroys and recreates ALL reverse references each time a node's references are updated (I guess in order to keep the 'vid' column in the CCK noderef table up to date?). I'm trying to build Partners for better scalability. It diffs the pre-save node with the post-save node (by storing a database of active node relationships) and only executes queries on the CCK tables for changed relationships. Right now, Partners is not particularly vid-aware. Its records about active bidirectional relationships and intermediary nodes only refer to the active revision of a given node. If you create a new revision of a node and eliminate a nodereference, the reverse reference and intermediary node (if applicable) will be deleted destructively. This may be rectified in a future version (revision?), but it's not high on my list right now given the use cases for which this is being developed.

Is this module usable for production? I'm tired of the bugs in cnr but the 0.x vers numbers really scare me.

Thanks.

I don't know of any bugs, but I'm still convinced that several probably exist. I've used the module quite a bit without problems, but there are a ton of different setups/use cases, so I can't guarantee rigorous testing has been done. The only thing I'm aware of that sucks is the admin interface.