I've done some more work on DB-based reports. It keeps some of the old
clunkiness, but does bring it all into the DB. I think the current
version now incorporates all of the functionality of a CFG file. The
code updates I've made are mostly self-contained, but there is a new
report_id field that I added to tbl_report_usage. I committed a db_mod
to git, but these were never my strong suit. :)
I've also written a script that will read an existing set of CFG files
and post them to the DB. It will preserve an existing report tree
(shelter, clinical, etc.) by storing the paths in the sortkey field.
I've tested it pretty carefully with the CFG files Nathan sent me, as
well as a couple I created, and I think it's pretty solid. (Solid as in
working. I freely confess that it's fairly ugly!)
If anyone at DESC gives this a test run, please post back what the
results were. Any feedback on this current implementation--especially
shortcomings or omissions I might not have caught--would be welcome.
Thanks.
Ken
|
