Make it a Behavior or (at least place in App Model). Certainly any kind of data access/manipulation does not belong in a component.
On Oct 31, 11:48 am, Skal Tura <[EMAIL PROTECTED]> wrote: > Doing those tasks inside model seemed messy way to it. > We have multiple models accessing portions of the data. > > Thought i showed quite clearly what this is upto :) > > So we have a text search engine, every snippet of text can have > multiple boolean type of modes, such as: removed and verified along > others. > Texts are in UTF8 because some is in normal latin1 charset, some are > russian or japanese. Therefore we have a field for romanised text > (normal alphabetic). > > That data is searched, used, and modified by multiple different > models, using slightly different criterias. > > There is 3 different models currently utilizing this component in a > way or an another. Every one of those models uses that component > differently, to output completely different things, from the same > data. > > On Oct 31, 3:54 pm, Adam Royle <[EMAIL PROTECTED]> wrote: > > > Well without any real examples it's hard to tell what you're doing. > > However I think most people would recommend you should do more inside > > your models. Components should just be to help out controllers with > > requests. > > > On Oct 31, 9:41 pm, Skal Tura <[EMAIL PROTECTED]> wrote: > > > > I am wondering did i chose the Cake way of doing things with this, or > > > atleast close :) > > > > We have multiple models, all of which access same set of tables > > > handling massive amounts of data, searched using fulltext indexes. > > > There's additions, searches, modifies etc. from 2 different models, ah > > > but there's a gotcha! Most of these searches are slightly different, > > > along with some of the inserts. > > > > So what i opted to do about handling this dataset is build an > > > component used by the controllers. This component rarely contacts the > > > model, and only one of the models for some assisting functions for > > > some metadata to attach to the actual dataset. > > > > Is the component way the cake way to do something like this? > > > > Different main search types is 4, with variations for 2 different > > > models. > > > Different inserts 1 with 2 variations. > > > Modifying pages 1. (Same form and everything, just some data used to > > > check to which model uses that data) > > > > So i've done a "simple" component with a helper class to handle all of > > > that :) > > > > Using cake 1.1 > > > > Main goal when i code is to get short, simple pieces of code together.- > > > Hide quoted text - > > > - Show quoted text - > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
