Sure, I only meant that the first model contains a fair bit of
information which isn't really related to that model. If you start
altering the other related models (adding or removing associations for
example) you need to go back and change the first model too.
Mind you, I'm doing this in a befor
So what I've figured out (i'm sure this is really obvious but I'm new)
is that i can reach into the associated models from the active model
and "unhook" what I don't need using unbind. Previously I was under
the impression I could only unhook direct assocaitions in the top level
model i was curr
There already is a ticket for what he's talking about:
https://trac.cakephp.org/ticket/980
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups
I'm guessing this quandary explains why most "easy" database
manipulation packages (say, FileMaker and Omnis) usually limit the
automatically-fetched associated records to one level deep. More
generally, I find that recursive fetching has a tendency to bring in
much more than I need. I have to go
I would open a ticket at http://trac.cakephp.org and explain the benefits
On 10/15/06, johnpfisk <[EMAIL PROTECTED]> wrote:
>
> I tried to do something similar using unbindModel on all the
> associations of the "other models associated".
>
> Probably not the best way to go about it as it has crea
I tried to do something similar using unbindModel on all the
associations of the "other models associated".
Probably not the best way to go about it as it has created a lot of
dependecies in the first model.
It would be nice to set the level of recursion in the association.
--~--~-~--~
You should be able to do this with unbindModel (and bindModel if you
want to add associations). Set a high $recursive level, but just
remove the unwanted assocations.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Wow, that's a really good question. It'll make the array resulting from
the findAll a lot easier to manage, and it'll probably be a lot more
efficient as far as the server's concerned. Can you post your models,
so we can understand more?
--~--~-~--~~~---~--~~
You
I have an app i'm starting to build. It has around 20 tables all
associated. The main table 'jobs' has several belongTo associations
and hasMany associations. I've found info on setting recursive and on
using unbindModel for controlling the results of findAll, etc.
What I want to do is call a f
