<?xml version="1.0" encoding="windows-1252"?>
<node id="453018" title="avoiding excessive number of methods in CGI::Application and DBI modules" created="2005-05-01 11:05:38" updated="2005-08-09 04:30:39">
<type id="115">
perlquestion</type>
<author id="405280">
aroc725</author>
<data>
<field name="doctext">
Recently I used the CGI::Application framework, as well as the DBI interface and the HTML::Template module to develop a survey Web application.
&lt;br&gt;&lt;br&gt;
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).
&lt;br&gt;&lt;br&gt;
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).
&lt;br&gt;&lt;br&gt;
Is there a(n easy) way to avoid this scenario ?</field>
</data>
</node>
