Even if I don't create the CRUD functionality, it's still there for another developer to totally mess things up. To add some level of protection I've created an AppReadOnlyModel that extends AppModel which has overridden save and delete functionality. It was easier than editing the beforeSave and beforeDelete callbacks of every model I wanted to make readonly.
Copong, Could you elaborate a little bit on the bind,unbind functionality and how it could be used here? Or point me in the direction I need to go in the vast internets to find said functionality? Unfortunately I'm using cake 1.2 which, while it does have an api, does not have any contextual manual written for it yet (to my knowledge). I don't remember this functionality being in 1.1. Thanks again! On Sep 5, 6:22 am, Copongcopong <[EMAIL PROTECTED]> wrote: > first, do the 1 table 1 model as suggested. > > > I need a way to have an object talk to these tables ... > > A Component will surely help on this. have this component (e.g. > GeoComponent) load the Models during initialization > Component::__construct(). > You may create different methods/functions for accessing the > information from the Models. > You may also prefer to use Model::bindModel()/Model::unbind() feature > so that you can dynamically alter the tables' association to minimize > table joins/queries. --~--~---------~--~----~------------~-------~--~----~ 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.com 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 -~----------~----~----~----~------~----~------~--~---
