you'll need to put loadModel at top of files also, just in case Class
is not available.
On Aug 14, 3:32 pm, "Pablo Viojo" <[EMAIL PROTECTED]> wrote:
> In short, use PHP OO inheritance
>
> Let's say
>
> class Model1 extends CommonFunctionalityModel{
> ....
>
> }
>
> class CommonFunctionalityModel extends AppModel{
> //common functionality to some of your models
>
> }
>
> --
> Pablo Viojo
> [EMAIL PROTECTED]://pviojo.net
>
> On 8/14/07, tinder01 <[EMAIL PROTECTED]> wrote:
>
>
>
> > Fairly new user with Cake, been experimenting with it for a couple of
> > days, now about ready to get some real work done - I'm currently using
> > the inheritance feature included in Postgresql 8.1. My database
> > contains several hundred tables inheriting from a set of parent
> > tables. Since I'd rather not implement and maintain several hundred
> > models and controllers, is there someway to implement some sort of
> > inheritance architecture to Models so that any changes made to a
> > "parent model" automatically propagates to "child models"? I'm mainly
> > concerned with data validation as well as custom view code associated
> > with shared columns.
>
> > Thanks.
>
> > -Ben
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
