So am I correct in thinking that this module "enforces" a relationship by forcefully creating the reverse lookup as another reference?

The Node Referrer module does a similar job by simply looking up other nodes which reference the node in question... There is no need for the enforced reference as the fact that A references B means that B refers to A.

Comments

OneTwoTait’s picture

OneTwoTait commented

subscribing... I was going to ask that too.

rokr’s picture

rokr
Location Bochum, Germany
commented

Node Referrer adds a read only field to list all back references - http://drupal.org/node/431308
What BackReference does sounds like a feature of corresponding node references module which i use for a couple of projects with great success. Maybe you have to check this out.

Just for the record. Another Module which is great for selecting nodes within a nodereference field and which adds some kind of backreferencing is node relationships

cheers, Ronald

jcfiala’s picture

jcfiala commented

Yes, there's similarities to Node Referrer.

But there are differences:

1) As my module uses actual nodereference fields, the cardinality of the relationships is enforced - if you want a 1 to many relationship between, say, articles and images, where each image can only be associated with one article, then that will be enforced, whereas Node Referrer, it seems, would allow the Image to show two articles related to it.

2) Since my module writes to the field, other modules can use that information - nothing else needs to know that backreference is there to act upon those values.

3) You can reference in either direction - you can reference an image from an article, or an article from an image. Node Referrer only allows you to set the relationship in one direction.

jcfiala’s picture

jcfiala commented
Status: Active » Closed (works as designed)

x