Flexible code generation

Ever have the feeling of déjà vu code—the feeling you've written those lines before?  That's probably because you did.  Most of the code we write follows one or another fairly predictable pattern: insert a row of data, scan the contents of an array, query a row for a primary key value, etc.

Wouldn't it be nice if you could simply select the appropriate pattern from a library and then apply it your database objects, generating code that fits your naming conventions, and your application data structures but also automatically follows best practices?

Welcome to the world of QCGU code generation!  QCGU takes code generation to a whole new level of flexibility and usability.  We provide a wide range of templates, to which you can add more of your own using our simple Code Generation Markup Language.  Our generation engine lets you easily select your database objects, provide script argument values, and more. Bottom line: with QCGU code generation, tasks that once took hours (and in some cases, days) will take minutes.

QCGU allows you to easily generate content (code, documentation, etc.) from the Oracle definitions of tables, views, packages, procedures and functions.  It is also fully extensible, so that you use other data resources to drive generation (if you can write a query in Oracle to represent the data you want, then you can use that data inside QCGU for generation).

And when it comes time to run your scripts, the QCGU Universal Run form gives you a wide range of options, including selection of objects against which to generate the script, script arguments that parameterize the output, and setup scripts that you can use to easily apply your own naming conventions to the code that is generated.

In the following screen, I am specifying a filter that will identify all tables that start with "EMP"; in other words, all my employee-related data structures.

After I run the script, I find that I have generated code for a total of eight tables, as you can see in this Results Window.

Scripts can also have arguments. When, for example, I run the script that will deploy my application, getting it ready for execution on top of QCGU elements, I am prompted to enter up to N values.  In this case, they all have default values, so I can accept those and proceed or change the values to fit my particular needs.

To sum up, QCGU code generation is the opposite of "one size fits all."  Instead, we have designed QCGU to make it adapt to your evolving and often very specific needs.  If you don't like our templates, you can write your own with the Code Generation Markup Language, a straightforward and powerful scripting language If you don't like our naming conventions, you can override them with your own approach, and they will be automatically applied to the existing scripts.