Details
Major Description
I had a weird transaction problem, where I couldn't manage to store a one-to-many relationship within a transaction.
This was quite misleading, because in fact, that was just a mapping problem.
I mistakenly used both foreignkey and remote-foreignkey pointing at the same column, though the remote-foreignkey wasn't needed since that was a one-to-many relationship and not a many-to-many relationship.
So the idea would be to add a sanity check to verify that you can't have both foreignkey and remote-foreignkey attributes pointing at the same column.