Merge changes in source code and unit test files
When BladeSmith finds existing source code and unit test files, it copies them to backup files before regenerating them. If you add SQL statements to unit test files and then regenerate them, BladeSmith merges your code automatically.
If the Merge property of the DataBlade® node in the Generate DataBlade dialog box is True, BladeSmith copies the changes you made to your source and unit test files into the newly generated source files. In this way, you can update your objects in BladeSmith without losing the code you added.
In source code files, BladeSmith does not remove code for routines that no longer exist in the project; you must manually remove such code. For example, suppose you create an opaque data type with an Assign() function specified and generate code; then you alter the opaque data type to no longer have an Assign() function. When you regenerate the source code, the Assign() function code remains.
If the Merge property of the DataBlade node in the Generate DataBlade dialog box is False, BladeSmith does not merge your previous changes into the new source files, but existing files are backed up. You can copy changes from the backup files into the newly generated files by using a text editor.
If BladeSmith encounters problems while generating files, it displays the Generate Code Problem dialog box. For help in resolving merging problems, click Help on this dialog box and read the online help.
For information about how to use merging to upgrade projects created with a previous version of the OneDB® DataBlade Developers Kit (DBDK), see the release notes.