Mike Fuller's Profile

Controllers are not the sole
source of all Model interaction. They do not exclusively police data.
Views can themselves pull up a Model without the Controller's permission
and retrieve data for presentation more efficiently.

In MVC, there is every indication that
Views should know about the Models they are presenting. Not just whatever
arrays we decide to spoon feed them from Controllers.

The intention was that a user could have multiple payments, and it seemed to make sense to define it using the foreignType parameter above, however when the model was built – this always related in a $this->hasOne(…) statement being created, because what was actually happening is that we were not defining the relationship at the other end, we were actually defining it at the local end! So foreignType: many actually means “Many users can have one payment” – hence the interpretation of $this->hasOne(..)