Yes, often I've thought the same as well, however when things change (add an extra model, add some extra fields) you're probably going to have to change this in multiple places. Plus, I've found it better to specify what you want, rather than what you don't want, when things may change in the future.
On Nov 25, 5:58 am, thatsgreat2345 <[EMAIL PROTECTED]> wrote: > I was curious if there was such a thing as notcontains, as sometimes I > just want to exclude a few fields, and sometimes the same fields such > as created / modified across a few tables. So it is some what of a > hassle to list out all the stuff for the contains parameter rather > then making something such as notcontains, or exlcude and have it > ignore those fields. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
