Yup I see what your saying. I think the light just switched on, in
fact it did Art's email confirmed it.
As all the way through out the old projects we never had a method
called setPersonRelationship, just setPerson we dropped the word
Relationship from the template. Doh ! Ohh well looks like its time
to hunt down all the cases where we did it the old way and change
them to use setAttributeNameRelationship instead.
Be aware that if you have a two-way relationship where one side is
light, and one side is heavy, i.e.:
user <--->> transactions
You might want to call transaction.setUser(u) over
transaction.setUserRelationship(u), because the relationship call has
to fetch all the transactions for a given user because its not smart
enough to notice that user->transactions() is a fault, so it can
ignore the "add" step for now...
