Version 0.18 released

0.18 (10/22/2005)

- Added table analysis of source tables prior to attempting to create the tables in the
destination database. Analysis consists of creating a test table with one column
in it for each column of the table. This can be turned off, but it gives a better description
of what happened in the event that a column name isn't allowed in the destination database.
Additionally, this will be done for all tables in the copy set before making any changes in the
destination database. If the source and destination databases are the same, this analysis is
skipped.

- Updated for SQuirreL plugin interface changes to be compatible with latest SQuirreL (> 2.0 final)
This version of the plugin is still compatible with previous versions of SQuirreL (2.0RC1, 2.0Final)
as the interface change added new members and did not change any existing members.

- Examined data types for the major dialects currently supported and explicitly set them for the
appropriate java type. Tested each type against the corresponding database for usage and
compatibility. This should hopefully make the default data type mappings used sufficiently
robust for compatibility between databases.(See
http://dbcopyplugin.sourceforge.net/dbcopydatatypemapping.html for more detail regarding how
the plugin maps data types between different databases)

- Fixed a bug that resulted in the following error message - "Copy failed: 0". Behind the scenes
an ArrayIndexOutOfBoundsException was encountered when getting information about the newly created
table in the destination schema, if the case of the table name didn't match.