Currently, calling the GET accessor of a hasOne association only allows criteria to be passed into the db driver.
This is different behavior than the hasMany GET accessors, which allows for Criteria and Options context.
Since settings like autoFetchLimit, Cache, etc are often situational, we would prefer to define this on the actually fetch, rather than in the original association declaration.
+1 - Extend hasOne to support both criteria and fetch options
Currently, calling the GET accessor of a hasOne association only allows criteria to be passed into the db driver.
This is different behavior than the hasMany GET accessors, which allows for Criteria and Options context.
Since settings like autoFetchLimit, Cache, etc are often situational, we would prefer to define this on the actually fetch, rather than in the original association declaration.
+1 - Extend hasOne to support both criteria and fetch options