Aha! I think what I will do is add "sister" methods:
- Parallel to data_array will be data_aref which returns an array reference AND the config object.
- Parallel to data_hash will be data_href which returns a hash reference AND the config object.
- Parallel to to will be toc which returns a $dbh AND the config object.
But I really need to think about where table information belongs... should it be with the database connection configuration information? Likely, it may be global to several such config nodes because you may have numerous ways to connect to the same database (ie, different attributes set, different hosts), but you want the table information to be the same across the various connection configurations.
It may or may not be wise to include the table information in the same file. This will require some reflection.
Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality