[Omaha.pm] Mapping Perl structures to a SQL table...

[Dan Linder <dan@linder.org>]

I'm taking on the task of converting our in-house tool to use the Perl
DBI module to replace the Data::Dumper/eval() it currently uses to
store and retrieve data.  Not pretty, but it has worked pretty well
for the small data sets we've been using.

We now have some people commenting on the speed - some have pages take
7+ minutes to bring up waiting for the back-end perl code to ripple
through the directory structure and eval() the necessary files to
build the page.  The "eval" function seems to be the bulk of the time
as I expected...

What I'm looking for is some general comments and discussion about the
mental task of mapping these hash tables into a SQL table.  I'm not
really looking for a tool, more a high level discussion about ways to
store the data and still remain flexible.

Dan

-- 
******************* ***************** ************* ***********
******* ***** *** **
"Quis custodiet ipsos custodes?" (Who can watch the watchmen?) -- from
the Satires of Juvenal
"I do not fear computers, I fear the lack of them." -- Isaac Asimov (Author)
** *** ***** ******* *********** ************* *****************
*******************