Migrating Classes

Introduction

Version 1.2 of the wizard introduced JDBC2 classes. Class migration is a one way process, which allows JDBC1 classes in the wizard to be migrated to become JDBC2 classes. Once migrated the classes are no longer JDBC1 classes: classes are moved, not copied.

Considerations

JDBC2 classes have some differences to JDBC1 generated classes. The code which uses JDBC1 classes should be reviewed to ensure no migration problems will occur.

• JDBC2 classes do not use "this." in the generated code. We do not anticipate problems on the whole. It is possible that clashes could happen if your classes extend wizard generated classes.
• JDBC2 classes generate a new set of methods and members to work on the scrollable resultsets. The new method names may clash if you have extended the database class.
• JDBC2 classes do not automatically close resultsets or statements. Existing code should ensure that close() is called on the JDBC2 generated class. The close method closes all the prepared statements and the resutlset. Individual close methods are also generated, to close the resultset alone, or individual select/insert/update/delete statements.

It is recommended that you create new JDBC2 classes and acquaint yourself with a few. Then when it comes to migration it is easier to understand what problems may or may not occur.

Migrating

The first step is to select which classes to migrate.

Next the JDBC2 settings are set. These settings apply to all the classes which are migrated.

Finally, the classes are migrated.