@Woodman:
Thanks you for the suggestions, I will try to set up a test using a
single Controller that dynamically calls the needed Model(s) and
View(s) for editing the objects and see how things perform.
@Coder:
Many thanks for the warning. You have a very good point about the
number of tables that will be created and the effect it will have on
searches and so on.
However, because I know there will not be (many) duplicate columns I
don't really see an alternative. If you do, please let me know.
Thanks again,
Rob
On 21 aug, 17:14, Angry Coder <[EMAIL PROTECTED]> wrote:
> Hi Bravo,
>
> I am not sure if going the route you have chosen will actually save
> you effort later, it might even cause some headaches.
>
> Won't each of these separate tables contain mostly the same columns?
> And if you want to search across entire classes of animals won't all
> of these tables cause more harm then good?
>
> As to answer your questions: (keeping in mind I am still new to
> cakephp)
>
> 1. I don't think so but it might make it more complicated. You might
> want to use some method of dynamically loading the models, if you plan
> to have so many.
>
> 2. You should be able to reuse some views by specifying which to load
> using:
>
> $this->render('name_of_template.thtml');
>
> within your controller functions.
>
> Cheers,
>
> Coder
>
> On Aug 21, 8:54 am, Bravo_Kernel <[EMAIL PROTECTED]> wrote:
>
> > Hi group,
>
> > I am building an application to (theoretically) store characteristics
> > for all existing lifeforms on this planet and need some conceptual
> > pointers on the best approach for solving this with Cake.
>
> > To keep things maintanable and extendible I am thinking of creating
> > lots of Models (with different database tables) using class
> > inheritance, for example:
> > classLifeForms -> classReptiles -> classSquamata -> classLizards
> > classLifeForms -> classReptiles -> classSquamata -> classSnakes
> > classLifeForms -> classMammals -> etc.
>
> > Assuming the Model approach is valid I will have to build hundreds of
> > Models. Now for my questions:
> > 1. Will this force me to build a different controller to handle adding/
> > deleting/modifying each subclass or would it be possible to reuse a
> > single controller?
> > 2. Will this force me to build a different view for each subclass or
> > is reusing an option here as well?
>
> > Any feedback is highly appreciated.
>
> > TIA Bravo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
