my $dyn_sql_maker = Some::Class->new( type => $cgi->param('type'), id => $cgi->param('id'), # etc ... ); my $sql = ''; $sql .= $dyn_sql_maker->select_clause . " Report-specific static SQL here "; $sql .= $dyn_sql_maker->from_clause . " Report-specific static SQL here "; $sql .= $dyn_sql_maker->where_clause . " Report-specific static SQL here "; $sql .= $dyn_sql_maker->groupby_clause . " Report-specific static SQL here "; # Do something with the SQL
The static stuff is based solely on which report you're running and not your type nor your id. The dynamic stuff is based solely on your type and id, but not which report you're running. And, these are 5-8 table joins with craziness heavily involved, so I can't use Class::DBI (Which is actually figuring into my resdesign of the schema ... I'm designing it to be able to use Class::DBI.)
Is there a module out there that will fit my needs? I'd rather not write one, if I didn't have to.
------
We are the carpenters and bricklayers of the Information Age.
The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6
... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
In reply to Navigating the plethora of SQL modules by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |