aroc725 has asked for the wisdom of the Perl Monks concerning the following question:
Recently I used the CGI::Application framework, as well as the DBI interface and the HTML::Template module to develop a survey Web application.
This approach worked very well, but the application needed only a couple of database tables (one for the survey answers and another for lookup values).
But if the application required say, 20 tables, and I needed 4 run-modes to implement 'CRUD' (Create/Read/Update/Delete) functionality for each table, then it would seem to me that I'd end up with 80 methods in my 'CGI::Application' module and another 80 methods in my DBI module. (The application module passes submitted form data to functions in the DBI module).
Is there a(n easy) way to avoid this scenario ?
This approach worked very well, but the application needed only a couple of database tables (one for the survey answers and another for lookup values).
But if the application required say, 20 tables, and I needed 4 run-modes to implement 'CRUD' (Create/Read/Update/Delete) functionality for each table, then it would seem to me that I'd end up with 80 methods in my 'CGI::Application' module and another 80 methods in my DBI module. (The application module passes submitted form data to functions in the DBI module).
Is there a(n easy) way to avoid this scenario ?
Back to
Seekers of Perl Wisdom