On Tue, May 20, 2008 at 2:29 PM, Michael Horne <[EMAIL PROTECTED]> wrote:
> > On the question of model components that map to tables, it's one of those > ideas that is good in principal. However, in principal, it only works right > up until that moment where you have a piece of business logic that crosses > over between two (or more) tables. For instance, take a property website. > You have one table for 'house' and one table for 'estate agent'. If you > want > the agent for that house, which model object do you put the function in. It > gets a bit arbitrary, but at least it has structure. In my opinion, if > you're going to do this, you have to be very strict with yourself and be > prepared to create 'gateway' model objects which can act as overarching > packaging objects for anything that doesn't fit your pattern. > > I don't know. Why can't we put it in both? Sam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
