Is it politically feasible to pick an existing tool that does the job of building the database and write an adaptor that goes from the INI format to whatever the existing tool wants? If you pick something that's well documented and supported, you just saved yourself an awful lot of work, and put a bunch of extra capability in the bank for when the INI approach runs out of steam.
You can name the resulting translator module Existing::Product::Schema::(From)?INI and release it or not as you choose.
In reply to Re: Assistance with naming a class
by pdcawley
in thread Assistance with naming a class
by Limbic~Region
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |