I LOVE PERL! However, if you value your job, you will step a bit further from the problem and try to find a good tool that will meet the needs of top management. There are several good OLAP tools used on data warehousing projects that can greatly simplify reporting if only you can develop datafeeds to their "cube" data model. Yes, it costs some money, but if there is a huge need for complex reports done quickly, OLAP is a good option.
Hacking it out yourself is both time consuming and counterproductive (assuming you don't go to the trouble of building Perl modules and stored procedures). The maintenance of lots of hacked stuff gets overwhelming very quickly.
Assuming you can't buy any tools, I suggest that at very least, you design Perl modules to control the interface to small groups of related tables. Your cgi code will be greatly simplified and your design process will be smoother. What works for me is to first design the tables, then design the interface .pm's and then to build the code that uses the .pm's.
That's just my opinion and I am very opinionated. So there.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
