> Hmmm ... my immediate problem with that is that as Class::DBI handles > relational database mapping, this could easily end up pulling in the > entire database!
I thought people typically modelled single records with their O/R classes. That's what I do. I don't create objects for data I don't need. > Part of the point of Class::DBI is that you don't load data until you > need it, so pre-populating a data structure with all the data you might > need isn't really a good fit... If you really have no idea what data you're going to call until you hit the template, then this is a problem. I am willing to make all the decisions about what data will be available for the page in the perl code before the template is called, so simply returning the already loaded data is good enough for me. This makes my sense with my design philosophy (all brains are in perl code, and templates are nothing but layout). - Perrin
