Yes John, I know what the AppModel is. But my idea is that instead of clogging your AppModel full of specific stuff that applies to only the few tables that Kabuto is talking about in this topic, you create a "container" model (that extends the AppModel for *application-wide* code) that holds the attributes/behaviors of just those tables. OOP is great for organizing code, if we slopped table-specific code in a file that our entire app uses, we might as well just ditch OOP and stick to procedural programming.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
