In the last example each person entity will have a person_set property when you
loop it
Also ->toArray() on a query is a good way to see what the result set contains
/Thomas
Sent from my iPhone
> On 19/08/2014, at 15.31, Dave Edwards wrote:
>
> Thanks for the replies,
>
> Having thought a
Thanks for the replies,
Having thought about it, I think that main thing that currently confuses me
is not the construction of the queries, but the process of getting to the
data once the object has been returned. Previously I could just drop a
pr($result) into the Controller or view and immedi
Exactly, but if you have been using 2.x for a long time, you have to "unlearn"
all the quirks. Once you do that things are much more intuitive in the new ORM
/thomas
On 19 Aug 2014, at 11:16, José Lorenzo wrote:
> I don't think it is, on the contrary, I feel that the ORM is much more
> appro
My answers are inline:
On Monday, August 18, 2014 4:59:42 PM UTC+2, Dave Edwards wrote:
>
> Hi,
>
> I'm having trouble getting my head around the new ways of working with the
> new ORM in CakePHP 3.
>
That's normal, given that you are a longtime CakePHP user, hopefully it
will make sense to you
In the first example you could call $query->toArray() to get an array of
article objects back.
The beauty is when you can start chaining stuff together, for instance custom
find methods
/thomas
On 18 Aug 2014, at 16:59, Dave Edwards wrote:
> Hi,
>
> I'm having trouble getting my head aroun
Hi,
I'm having trouble getting my head around the new ways of working with the
new ORM in CakePHP 3.
I understand that an object is now returned instead of an array, but I find
the amount of new Documentation to explain the new methods of working with
Models almost overwhelming. Whilst it is c
