Intermediary Language Debugging

The script from an MDA template produces intermediate language text. However, on generating the model this script could return errors. When an error occurs, you can view and debug the generated text externally, preferably in an editor that prompts on updates to the file alterations.

Access    Project Browser | Right-click on Package | Advanced | Transform Package  (Ctrl+Shift+H)


For a MySQL database, the template code might resemble the following:

$enumFieldName = �test�




   name=%qt%%CONVERT_NAME($enumFieldName, "Pascal Case","Camel Case")%%qt%




This returns the output in the generated text file as:




 name = "test"

 type = "ENUM"



If there is an error in the original transform, such as a spelling error - �Colum� - clicking the Do Transform button returns an error message referring to the first line of intermediate code that includes the error 'Colum�.

Debug when errors are returned on generating altered code



See also


Select the Package to be transformed, and the Transform Package option.

The Model Transformations dialog displays.


Transform Elements


In the Name column, select the checkbox against the type of transformation being altered.




In the Intermediary File field, click on the ( ... ) button and set the file location into which to generate the code.




Select the Write Always checkbox, and click on the Write Now button to generate the script.

This only generates the script, not the model.




If an error is returned specifying the line number of the problem, open the file in an external Code Editor (with Line Numbering) and locate the line number of problem.




Alter the template code to correct the error.




Click on the Do Transform button to check that the alteration has corrected the problem.