(4) sounds good, maybe another option to avoid getting configHelper too
crowded is to create subclasses of ConfigHelper to handle more commonly used
scenarios, and users would use those specialized classes for specific
scenarios... but, as mentioned by Kevin, (4) is fine for now, and we can
Currently, the DAS has a ConfigHelper to allow users to build up DAS
Config without using an XML file. However, its function today is
limited to adding a table, relationship, primary key, or update
statement to the config. This needs to be fleshed out, but I think if
we follow down the current
