Donate Share

SQuirreL DB Copy Plugin

File Release Notes and Changelog

Release Name: DBCopy-0.20

Notes:
Please note that the archive files marked 
"squirrel1.2beta6-compat" are only to be used with 
SQuirreL 1.2beta6.  They will not work with any other
version of SQuirreL.  The other files can only be used 
with SQuirreL versions 2.0 and higher.

This plugin provides

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

- Includes Primary Key, Foreign Key constraints and 
  indexes for tables copied.

- Uses Hibernate 3.0 internally to perform database 
  object type mappings.
  Supported Databases are: 
        Axion, DB2, Derby(Cloudscape), Firebird, 
        Frontbase, HyperSonic(HSQLDB), Ingres, 
        McKoi, MySQL, MS SQLServer, Oracle, 
        Pointbase, PostgreSQL, Progress, Sybase ASE

- Allows the 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.

- A progress dialog is displayed during copy which 
  allows the user to cancel the operation and shows 
  progress for records on top and tables on the bottom.

Changes: 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. - Added support for the Progress, FrontBase and Ingress RDBM servers. - Added ability to disable copying Primary Keys (Axion build M3 doesn't have the ability to get primary key information). - Used DBMonster (http://dbmonster.kernelpanic.pl/) to generate a test set for DBMonster-supported types. This yielded another round of tweaking the specification of types to use in Hibernate for determining the destination database table definitions. The result is a more precise algorithm for determining what field type and length to use when the destination database table doesn't exist before copying. - Fixed bug #1355029 (Copying BLOBs to MySQL sometimes fails) - Fixed bug #1365782 (null values converted to O) - Fixed bug which caused TIME columns to be copied into MySQL as DATE instead. (The value would appear to be 0000-00-00, regardless of this actual value in the source database) - Fixed bug #1369033 (In Sybase, nullable fields are created as NOT NULL)