good chemistry is complicated,
and a little bit messy -LW
pluggable/dynamic data processing/munging/transforming module?by rwstauner (Acolyte)
|on Nov 16, 2010 at 18:44 UTC||Need Help??|
rwstauner has asked for the
wisdom of the Perl Monks concerning the following question:
Oh wise and varied monks, I come seeking the existence of yet unknown modules.
I have to clean up some gross, ancient code at $work, and before I try to make a new module I'd love to use an existing one if anyone knows of something appropriate.
At runtime I am parsing a file to determine what processing I need to do on a set of data.
If I were to write a module I would try to do it more generically (non-DBI-specific), but my exact use case is this:I read a SQL file to determine the query to run against the database. I parse comments at the top and determine that
So when fetching from the db the program applies the various (possibly stacked) transformations before returning the data.
Currently the code is a disgustingly large and difficult series of if clauses processing hideously difficult to read or maintain arrays of instructions.
So what I'm imagining is perhaps an object that will parse those lines (and additionally expose a functional interface), stack up the list of processors to apply, then be able to execute it on a passed piece of data.
Optionally there could be a name/category option, so that one object could be used dynamically to stack processors only for the given name/category/column.
A traditionally contrived example:
Each processor (gsub, date, exchange) would be a separate subroutine. Plugins could be defined to add more by name.
So the obvious first question is, does anybody know of a module out there that I could use? About the only thing I was able to find so far is Hash::Transform, but since I would be determining which processing to do dynamically at runtime I would always end up using the "complex" option and I'd still have to build the parser/stacker.
Is anybody aware of any similar modules or even a mildly related module that I might want to utilize/wrap?
If there's nothing generic out there for public consumption (surely mine is not the only one in the darkpan), does anybody have any advice for things to keep in mind or interface suggestions or even other possible uses besides munging the return of data from DBI, Text::CSV, etc?
If I end up writing a new module, does anybody have namespace suggestions? I think something under Data:: is probably appropriate... the word "pluggable" keeps coming to mind because my use case reminds me of PAM, but I really don't have any good ideas...