laziness, impatience, and hubris | |
PerlMonks |
Re: avoiding excessive number of methods in CGI::Application and DBI modulesby dragonchild (Archbishop) |
on May 02, 2005 at 12:46 UTC ( [id://453196]=note: print w/replies, xml ) | Need Help?? |
Is there a(n easy) way to avoid this scenario ?
Yes - don't design your application in a way that sucks. You're thinking as a DBA / programmer, not as a systems analyst. Think about how your application is going to be used. CGI::Application (and similar frameworks) provide user-level mapping to business-level concepts. I had an application that would CRUD over 40 tables. But, because there were only 7 different screens (with options), I had 7 runmodes. Now, based on those options, different things would happen. Here's another way to look at it - to run reports, I need 2 runmodes - PickReport() and RunReport(). However, I will probably want:
In total, I think we ended up with some 250 files supporting 70 reports. Still only 2 runmodes, though ... The Perfect is the Enemy of the Good.
In Section
Seekers of Perl Wisdom
|
|