This method I'm working with to support #34 uses an XML document that describes the blueprints, with modifications and relationships, on HOWTO build all of the templates (using helper templates).
Storing the XML document as a Template should allow easy transportation of the blueprint. (eg as part of an oddgen generator)
This should also allow the deployment of CLOB-like data using only SQLPlus/SQLDeveloper/SQLcl as part of an installation package. (eg the XML document that represents the default helper templates can be loaded as part of the install.sql script for tePLSQL.)
This method I'm working with to support #34 uses an XML document that describes the blueprints, with modifications and relationships, on HOWTO build all of the templates (using helper templates).
Storing the XML document as a Template should allow easy transportation of the blueprint. (eg as part of an oddgen generator)
This should also allow the deployment of CLOB-like data using only SQLPlus/SQLDeveloper/SQLcl as part of an installation package. (eg the XML document that represents the default helper templates can be loaded as part of the
install.sqlscript for tePLSQL.)