its not intuitive at all.
And now i need to do major rewrite of the app... i hoped some1 would
tell its only RC2 "feature" and in live it s going to be as it should
be...
Check out the new CakePHP Questions site http://cakeqs.org and help others with
their CakePHP related questions.
You received
The reason for the empty hasOne relation is because Cake LEFT JOINs
the relation and doesn't check for an empty record before returning
the array. You can specify INNER if you want when declaring the
relationship, but then if the related record is empty nothing will be
returned. I suspect that's wh
The blank hasOne array (with all of the empty keys) has always struck
me as the most counter-intuitive thing ever. An empty relation should
be completely empty. If this is now the case with belongsTo (I haven't
tested), then that seems to be a step backwards.
On Mar 24, 4:19 pm, RobertMeisner wr
has something changed in ver 1.3 coresponding to how empty relations
are presented?
Whenever i use 0 or null as foreign-key i get something like (so its
same as it's always been with hasOne relations):
[Webpage] => Array
(
[id] => 1
[created
