<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent posts to news</title><link>https://sourceforge.net/p/dbcopyplugin/news/</link><description>Recent posts to news</description><atom:link href="https://sourceforge.net/p/dbcopyplugin/news/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 02 Jan 2007 16:10:08 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/dbcopyplugin/news/feed.rss" rel="self" type="application/rss+xml"/><item><title>Version 1.1 Released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2007/01/version-11-released/</link><description>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:

It now includes support for Informix and Sun HADB databases. 

Version 1.1 Bug-Fixes:

\- Removed reflective code used for backward compatibility which was causing 
IllegalAccessExceptions when the keyword test was applied to column names.

\- Fixed bug in copying FK constraints which left cursors open by not properly 
closing ResultSets when they were no longer needed.

\- Fixed bug in copying FK constraints where the primary key table 
name wasn't fully qualified the schema of the destination database.  This was 
most noticeable when copying tables with FKs into a schema which was not the 
default schema for that session.

\- Fixed bug where cancelling the copy operation during table data transfer 
did not also cancel the transfer of table constraints.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Tue, 02 Jan 2007 16:10:08 -0000</pubDate><guid>https://sourceforge.net65480894a852502043f4d7ffa6f01e423c3dd695</guid></item><item><title>Version 1.0 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/10/version-10-released/</link><description>
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.  
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 07 Oct 2006 15:51:40 -0000</pubDate><guid>https://sourceforge.net90662a85dbe2a08506f0c042ae54e79a32f5018a</guid></item><item><title>Version 0.25 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/08/version-025-released/</link><description>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\) 

Changes in release 0.25 of DBCopy plugin were:

\- Previously, when copying from Axion and &amp;quot;Copy Primary Keys&amp;quot; or 
&amp;quot;Copy Foreign Keys&amp;quot; was selected, the copy operation would fail with 
SQLException stating the following: 

&amp;quot;getPrimaryKeys\(\) is not supported&amp;quot;

&amp;quot;getImportedKeys\(\) is not supported&amp;quot;

Now, when using Axion as the source database, the copy operation will ignore 
the user's preference for these settings, since it is not possible to honor 
them with Axion and complete the copy operation.

\- When selecting tables to copy, the user can now select the &amp;quot;TABLES&amp;quot; folder
which will mark all tables contained in that schema for copy.  Previously, 
the user would have to expand the tables folder and select all tables 
manually.  Similarly, the &amp;quot;TABLES&amp;quot; folder has also become a &amp;quot;target&amp;quot; for 
paste operations.

\- Added support for TimesTen 6.0 \(Note: fetch size for TimesTen is max 128.
If the preference is set to larger than this, 128 will be used\)

\- Bugfix: In getting the qualified name of a table \(schema.table\) when the
schema was an empty string, the qualified name would appear to be &amp;quot;.table&amp;quot;

\- Bugfix: Added CLOB type to the list of types for which clearParameters must
be called prior to setting parameters when null and non-null values are used
for MySQL driver.

\- Bugfix: Use the same logic to determine the source column type for &amp;quot;OTHER&amp;quot; 
type when inserting records into destination, as is used to determine what 
types to use for creating the table in the destination database.  Previously,
the &amp;quot;OTHER&amp;quot; type resolution was only being done for table creation and not 
for record insertion.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sun, 27 Aug 2006 18:07:34 -0000</pubDate><guid>https://sourceforge.netdfea886fedfee9a2bf37af853491750a32349f88</guid></item><item><title>Version 0.24 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/07/version-024-released/</link><description>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\)

Changes in release 0.24 of DBCopy plugin were:

\- Fixed bug \#1468056 \(Missing i18n string argument\)

\- No longer use class names of the jdbc driver to decide which dialect 
to use.  Now we use database product name and version.  This should be
a more accurate method for determining which dialect to use for source 
and destination sessions, prompting the user less often.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sun, 23 Jul 2006 22:45:24 -0000</pubDate><guid>https://sourceforge.net1cb0548fa5db52eddf0a1cb1780ea4f73752692f</guid></item><item><title>Version 0.23 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/04/version-023-released/</link><description>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.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 08 Apr 2006 01:17:04 -0000</pubDate><guid>https://sourceforge.net966e5ba4c5eb70df0482a44eff07508da9ac225c</guid></item><item><title>Version 0.22 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/03/version-022-released/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 18 Mar 2006 16:12:10 -0000</pubDate><guid>https://sourceforge.net862908c60d9d7b3f336541d79db19d7639e2a39d</guid></item><item><title>Version 0.21 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2006/01/version-021-released/</link><description>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 &amp;quot;table &amp;lt;X&amp;gt; not
found&amp;quot; error message.

\- Fixed bug \#1398199 \(Copying large tables from MySQL causes SQuirreL to 
run out of memory\)

\- Fixed bug \#1386606 \(Copying tables with BLOB columns to Pointbase fails\)
Now using ps.setNull instead of ps.setBytes for null values.

\- Fixed memory leak caused by undisposed progress dialogs.

\- Added elapsed time counter and time remaining estimate to the progress 
dialog. 

\- Added independently configurable delay \(in millisecond granularity\) between
copying records and tables.  This reduces the load \(cpu and io\) on both 
the client and the database server\(s\).

\- Better support for BOOLEAN types when the source database supports them
and the destination database does not.

\- Updated DBCopy plugin help screens that are available in SQuirreL via 
the help menu.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 21 Jan 2006 23:41:16 -0000</pubDate><guid>https://sourceforge.netcdf9e0c4cdb9bdd36900a63741e282f82cab4c3b</guid></item><item><title>Version 0.20 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2005/12/version-020-released/</link><description>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.

\- Added support for the Progress, FrontBase and Ingres 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\)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 10 Dec 2005 16:04:22 -0000</pubDate><guid>https://sourceforge.net44ba72b4c7a36213085be1ea25b6f9279e141551</guid></item><item><title>Version 0.19 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2005/11/version-019-released/</link><description>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.

\- Added custom type mappings for McKoi, Derby and Sybase

\- Fixed bug which caused multiple dialogs to appear when cancelling a copy operation.

\- Fixed bug that would create a temporary file to store the blob in if the blob column
value is null.

\- Fixed bug 1344224 \(When auto-commit is disabled, committing the source session\)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sat, 05 Nov 2005 00:41:23 -0000</pubDate><guid>https://sourceforge.net16f3deda62175651060548968173841d6be461d2</guid></item><item><title>Version 0.18 released</title><link>https://sourceforge.net/p/dbcopyplugin/news/2005/10/version-018-released/</link><description>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 \(&amp;gt; 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 - &amp;quot;Copy failed: 0&amp;quot;.  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.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Manning</dc:creator><pubDate>Sun, 23 Oct 2005 02:48:55 -0000</pubDate><guid>https://sourceforge.netad0650506ad8f0838834bcf677e7cbbdb62866d2</guid></item></channel></rss>