> The salient aspect of relational data is that it's cyclic This is an odd claim. Most relational data is not cyclic, and it's easy enough to come up with a sc

> The salient aspect of relational data is that it's cyclic This is an odd claim. Most relational data is not cyclic, and it's easy enough to come up with a scheme to handle cyclic data in a consistent fashion. Conflicting changes (two changes to the same 'cell' of a database table) are a much more likely issue to hit and will need handling in much the same way merge conflicts are currently handled, so there are already situations in which manual effort will be needed.