D.2. Migrating from Kodo 3.0 to Kodo 3.1
Prev | Appendix D. Upgrading Kodo | Next

## D.2. Migrating from Kodo 3.0 to Kodo 3.1

The following are points to consider when upgrading from Kodo 3.0.x to Kodo 3.1.0:

- Kodo now uses its own logging framework by default instead of the Commons Logging framework. To use the Commons Logging framework as in older versions of Kodo, set the `kodo.Log` property to `commons`. See Chapter 3, Logging for details.

- The DBDictionary now supports the `DefaultSchemaName` parameter. See Section 4.3, “Database Support”. The default is `null`, which will cause Kodo to check all schemas for unqualified tables. Setting this will cause Kodo to only check the specified schema for unqualified tables. `kodo.jdbc.Schemas` is now only used in conjunction with reverse-mapping processes to identify which schemas to examine for reverse mapping.

Prev | Up | Next
Appendix D. Upgrading Kodo | Home | D.3. Migrating from Kodo 3.1 to Kodo 3.2