Active
Project:
BackReference
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Oct 2009 at 21:46 UTC
Updated:
2 Oct 2009 at 22:36 UTC
Saying backreference is "for maintaining 1-1 relationships" is an insufficient warning that it very much shouldn't be used in any other context. Applying backreference to many-1 relationships will force them to be 1-1 by deleting previous references to the same node. Because backrefence also doesn't create a new revision when making changes to the referenced node, the lost data can not be recovered. This at least needs a clear warning. Better yet, it should check for many-1 relationships and not apply to them.
Comments
Comment #1
sreynen commentedOn further testing, references are only deleted when multiple nodes reference a node with a singular back reference field. This could probably be auto-corrected by backreference, but it should at least trigger a warning. Deleting the previous backrefence and the associated reference, as it does now, results in silent data loss.