Marco,
For some of our custom DDL templates, the user is prompted for a few things like application code, table code and table name. These are used to pre-populate a bunch of stuff in the DDL script that creates the table, sequence, table/column comments and constraints. I don't know beforehand whether they will reply with uppercase, lowercase or mixed case answers.
Due to our script and naming standards, some things should be lowercase and others are uppercase to pass script review.
It would be nice if I could take what was entered by the user in the template dialog and apply upper or lower case to it in the points of the template where that case is needed. Although some would scoff at this feature (since Oracle objects are case-insensitive), this feature could be used effectively in PL/SQL templates where many shops have upper/lower standards for built-ins vs. application identifiers, etc.
For some of our custom DDL templates, the user is prompted for a few things like application code, table code and table name. These are used to pre-populate a bunch of stuff in the DDL script that creates the table, sequence, table/column comments and constraints. I don't know beforehand whether they will reply with uppercase, lowercase or mixed case answers.
Due to our script and naming standards, some things should be lowercase and others are uppercase to pass script review.
It would be nice if I could take what was entered by the user in the template dialog and apply upper or lower case to it in the points of the template where that case is needed. Although some would scoff at this feature (since Oracle objects are case-insensitive), this feature could be used effectively in PL/SQL templates where many shops have upper/lower standards for built-ins vs. application identifiers, etc.
