[Klimapol]

I'm finally sure that I've nailed down my problem, and I think I mean it this time. I'm not going to call it a bug just yet, more of a
Inconsistancy. I have 2 models, say A hasMany B and B has a afterFind() in the model class. When doing a a->read() it ends up calling the
B->afterFind() when getting the data. The inconsistancy is that when b->read() is called the structure of $results passed into the function is
$results['name']['field']='value' but when b::afterFind() is called from a->read() the structure of $results is $results['name'][0]['field'] = 'value' .
Because of the hasMany the structure of the data makes sense, but I'm curious if you intended the afterFind() to have to cope with receiving differently
Formatted structures from associations.

[Poolkop]

B->afterFind is still called
A I mean
But b is last
Set recursive = 0 or -1

[Klimapol]

Right, but the $results has an extra dimention and the handling logic needs to be different to handle it if coming from an association,
It seems undesireable to have to code that logic into the afterFind to me, and I wanted your point of view. am I clear in explaining what data I'm seeing?
When b->read() is called the structure of $results passed into the function is $results['name']['field']='value' but when b::afterFind() is called from a->read() the structure of $results is $results['name'][0]['field'] = 'value' .
So my foreach($results is breaking on the association because it has the extra dimention.

[Poolkop]

The structure is correct
They way it is returned

[Klimapol]

I understand the structure, and it makes sense because of the hasMany.

[Poolkop]

What are you trying to do in the afterFind?

[Klimapol]

The problem is when $results is a 3? dimention array, from the association, and a 2 dimention array from the model itself.

[Poolkop]

You need to take that into account with your code Klimapol
Like I said, set recursive to 0 or -1 so the hasMany are not returned

[Klimapol]

Right, I was jsut typing, if it was your opinion of people should have to do so.

[Poolkop]

Yes
The core sends it to your methods in a set format
This is consistent across the board

[Klimapol]

Ok, that is fine, I just wanted to help bring it to your attention if it was not supposed to be that way. it is kind of dificult to track down, when creating a afterFind() function I would not expect that it would get different data structures. but like I said, the hasmany structure made perfect sense, just handling it seems out of place compared to the rest of cake.
Thank you for your time. and hopefully that is my last major question for a while.