SQuirreL DB Copy Plugin / News: Recent posts

This version (1.1) is only available in SQuirreL SQL Client (version 2.4) installer (and optional archive). SQuirreL version 2.4 can be downloaded from here:

http://sourceforge.net/project/showfiles.php?group_id=28383

As of version 1.1, DBCopy plugin will no longer be made available seperately from the SQuirreL installer as it is no longer backward compatible with previous releases.

Version 1.1 Enhancements:... read more

This release has relatively few changes which
were a result of running the code through
findbugs(http://findbugs.sourceforge.net/) a
most excellent quality assurance tool.

This new release will also appear as an
optional plugin in the SQuirreL 2.3
final installer, making it unnecessary
to download the plugin and install it
separately as with previous releases.
Still this version is being made available
here for those who wish to stick with the
version of SQuirreL that they have. Please
be sure to choose the correct plugin archive
file (the *compat* files are only to be used
with 1.2beta6 - they will not work with
SQuirrel 2.x) ... read more

This new release will also appear as an
optional plugin in the SQuirreL 2.3
final installer, making it unnecessary
to download the plugin and install it
separately as with previous releases.
Still this version is being made available
here for those who wish to stick with the
version of SQuirreL that they have. Please
be sure to choose the correct plugin archive
file (the *compat* files are only to be used
with 1.2beta6 - they will not work with
SQuirrel 2.x)... read more

0.23 (04/07/2006)

- Added support for MaxDB 7.6 (open-source re-branding of SAPDB)

- Fine tuning of the precision mechanism added in the previous release
for some drivers which report erroneous sizes and precision of number
and char datatypes.

The following changes were made from 0.21.

0.22 (03/18/2006)

- Added support for DaffodilDB and H2 (www.h2database.com)

- For number type fields, previously, the precision was always the
maximum allowed by the destination database. A new mechanism was
added to allow the source database precision to be used if it
doesn't exceed the destination database's maximum precision.
Otherwise the previous behavior (maximum precision allowed by the
destination database) is used.

The following changes were made from 0.20.

0.21 (01/21/2006)

- Tested binary data copy using newly developed BinaryGenerator plugin
for DBMonster.

- Fixed a bug where copying to MySQL when the table exists in a catalog
other than the one in the connect URL would result in a "table <X> not
found" error message.

- Fixed bug #1398199 (Copying large tables from MySQL causes SQuirreL to
run out of memory)... read more

The following changes were made from 0.19.

0.20 (12/10/2005)

- Added the ability to copy to existing table definitions that differ from
the source table definitions with regard to column order (columns are now
matched up by name instead of assuming they are in the same order on the
destination database as that of the source database).

- Added support for the Axion (build M3) Java embedded database.... read more

0.19 (11/04/2005)

- Performance increase due to a reduction in the number of data-type queries on the source
and destination databases (Thanks to Dan Dragut)

- Fixed table analysis progress monitor dialog so that it goes away when the copy operation
is complete.

- Examined data types for the other dialects (Firebird, HyperSonic, Pointbase, etc.)
currently supported and explicitly set them for the appropriate java type. Tested each type
against the corresponding database for usage and compatibility.... read more

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.... read more

0.17 (8/26/2005)

- Added configuration item for column name keyword checking in destination database.
This feature uses the "keywords" reported by the JDBC driver to find column names
in the source table copy set that cannot be used as column names in the destination
database. However, this is too aggressive in some cases as some databases (like DB2)
report keywords that can also be used as column names. So, now this checking can be
disabled. The configuration is available in ... read more

0.16 (8/21/2005)

- Added custom column type mappings for IBM DB2. (Tested against DB2 PE for Windows)

- Added new configuration option to disable auto-detection of destination
database.(This causes the Hibernate dialect chooser to always appear when
copying to a new database session. Dialect choices are cached for existing
sessions). The configuration is available in

"Global Preferences" -> "DBCopy" -> "Column Type Mapping"... read more

Changes include:

- Added support for caching BLOBs to disk during transfer to prevent
the client from running out of memory on large BLOBs. Transfer buffer
size is configurable.

- Added DB Copy tab to Global Preferences section of SQuirreL to configure
preferences for the DB Copy Plugin.

- Truncate can now be used for databases that support it, instead of "delete".
This can be turned on/off for all databases in the preferences. If enabled
it will be attempted, and if not supported, delete will be used instead.... read more

The following changes were made.

0.13 (7/30/2005)

- Added support for copying index definitions along with the tables
that are being copied.
- Altered destination table truncation to use "delete from" instead of
the less standard "truncate table". Will add support for this back
in on some databases in the next release.
- Added check for if column is a keyword when copying data from one
table to another (In the case where the data is copied without creating
the table).
- If an SQLException is encountered during record copy, show it's message
to the user (instead of simply printing the stack trace).
- Fixed source files eol chars. What a pain!!!
(WinCVS - checkout with Unix LF - why is this the default now???)

The following changes were made:

0.12 (7/13/2005) First Beta Release

- Added support for internationalizing the the user dialog messages.

- Bug fixes (moved GUI work onto event dispatch thread)

- Added support for checking if source database column names are in fact
keywords in the destination database.

- When records exist in the destination table, the delete dialog now indicates
the name of the table when asking the user if it should truncate the table.... read more

- Added copying table constraints (Primary Key and Foreign Key).
- Added dialog to allow user to select a hibernate dialect for the destination
database, if one couldn't be determined automatically.
- Asks user to truncate records in destination table, if records already exist.
- Fixed packaging to place hibernate and commons-logging jars in subdirectory
space of dbcopy plugin.
- Supported Hibernate dialects are now:
Firebird, Oracle, Sybase, MS SQLServer,
MySQL, HyperSonic, Pointbase, PostgreSQL.
- Bug fixes. Actually tested this release a bit.

This plugin provides

- Copy and Paste tables from one session to another (Can be different database
types (MySQL -> Oracle, SyBase->MySQL, etc...)

- Uses Hibernate 3.0 internally to perform database object type mappings.

The "Copy Table" and "Paste Table" functions are accessible through
the context-sensitive (right-click) menu of the Object Tree. See
readme.html for example usage.... read more