v2.2.0

New features:

• Oracle: Convert SDO_geometry column content to GML #343
• Skip the import/export of specific columns #342
• Support the new SIARD 2.1 #329
• Add support for arrays #129

Enhancements:

• Inversion of control in module loading #361

Bug Fixes:

• Undefined datatypes error when migrating view from another DBMS #345
• Error converting SQL Server timestamp field #322

---

Using the new features:

To extract GML files from SDO_GEOMETRY cells in Oracle DBMS

• Use the parameter -egml <directory> or --export-gml-directory=<directory> to specify the directory in which the GML files should be created;
• The GML directory parameter can be used when exporting to SIARD 2 (version 2.0 and 2.1);
• One GML file is created per table (and only for tables containing SDO_GEOMETRY data).

To skip the import/export of specific columns

Documentation about this feature is available at project-wiki/List-Tables-Module

To use the new SIARD 2.1

• In the import module
  No action needed. DBPTK will auto-detect the SIARD 2 version.
• In the export module
  Defaults to version 2.1;
  2.0 can still be used by using the -v 2.0 or --siard-version 2.0 parameter.
• Extra functionality
  When using any SIARD modules, the versions are logged before the migration starts like:

  Importing SIARD version 1.0
  Exporting SIARD version 2.1
  

v2.1.0

New features:

• Support exporting database, schema, table and column descriptions #174

Enhancements:

• Oracle schema/tablespace error. #215

Bug Fixes:

• NPE when migrating schema without tables #369
• Possible bug in sql-server module, failing to get SQL for views #327
• Using -ede still tries to use encryption in postgresql export module #286
• Exporting to mysql error: Packet for query is too large #251

v2.0.1

Enhancements:

• Core and module improvements #366
• Use Oracle maven repositories #364
• Configure continuous integration and deployment #362

Bug Fixes:

• Possible bug in sql-server module, failing to import triggers. #325
• ORA-01000: maximum open cursors exceeded #315

v2.0.0

Enhancements:

• Improved reporting

v2.0.0-rc2

Enhancements:

• Improvements related to the Database Visualization Toolkit

Bug Fixes:

• See commit messages

v2.0.0-rc1

New features:

• Stores files in folders inside the dbptk home directory:
  • a folder for reports (reports)
  • a folder for logs (log)
  • a folder for module data (modules)
    • currently only the solr export module uses this folder, but it may be used in the future to store temporary and other module-related files
• The dbptk home directory is:
  • a folder dbptk inside the current directory (by default)
  • the value defined in the dbptk.home java system property

Enhancements:

• Improvements related to the Database Visualization Toolkit

Bug Fixes:

• See commit messages

v2.0.0-beta7.2

Enhancements:

• Improvements in Solr module
• Improvements in MS Access module.

Bug Fixes:

• See commit messages

v2.0.0-beta7.1

Enhancements:

• Improved Solr module

Bug Fixes:

• See commit messages

v2.0.0-beta6

Enhancements:

• All modules: Better use of computing resources;
• SIARD modules: Better handling of temporary files;

Bug Fixes:

• See commit messages

v2.0.0-beta5

New features:

• Solr: includes Solr export module used by Database Visualization Toolkit

Enhancements:

• All modules: Better use of computing resources

Bug Fixes:

• All modules: Better handling of NULL values
• Multi-schema DBMS: Better handling of multiple schemas
• MS SQL Server: fixes connection issue in export module
• MS SQL Server: attempts to obtain SQL statement used to create views
• Oracle: fixes exporting of tables with primary keys