summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEike Stepper2007-10-20 08:59:46 (EDT)
committerEike Stepper2007-10-20 08:59:46 (EDT)
commita848a9eb88a6ab7bf458e9cd58c63d62e4ec7ca0 (patch)
treed443ca9fccf5c377f8cb275d85d0d371578b907d
parent7840ac9ea1a4e11c7b812704b44516b34ef0398d (diff)
downloadcdo-a848a9eb88a6ab7bf458e9cd58c63d62e4ec7ca0.zip
cdo-a848a9eb88a6ab7bf458e9cd58c63d62e4ec7ca0.tar.gz
cdo-a848a9eb88a6ab7bf458e9cd58c63d62e4ec7ca0.tar.bz2
New DB adapters
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/.classpath8
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/.cvsignore1
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/.options4
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/.project28
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/META-INF/MANIFEST.MF13
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/about.html28
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/build.properties24
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/copyright.txt8
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/epl-v10.html319
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/fragment.properties25
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/fragment.xml29
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/.cvsignore1
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_2.txt813
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_3.txt45
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_8_0.txt529
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_1.txt304
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_2.txt532
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_8_0.txt287
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/databaseinjar.txt59
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlFindFile.html29
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlSoftwareLinks.html36
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/hsqldb_lic.txt31
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/hypersonic_lic.txt66
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/readme-docauthors.txt115
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/readme.txt4
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/lib/readme_linux.txt12
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/license.html319
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/HSQLDBAdapter.java34
-rw-r--r--plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/bundle/OM.java44
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/.classpath8
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/.cvsignore1
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/.options4
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/.project28
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/META-INF/MANIFEST.MF13
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/about.html28
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/build.properties24
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/copyright.txt8
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/epl-v10.html319
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/fragment.properties25
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/fragment.xml29
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/.cvsignore1
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/CHANGES3753
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/COPYING343
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/EXCEPTIONS-CONNECTOR-J119
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/README45
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/lib/README.txt45
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/license.html319
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/MYSQLAdapter.java45
-rw-r--r--plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/bundle/OM.java44
49 files changed, 8948 insertions, 0 deletions
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/.classpath b/plugins/org.eclipse.net4j.db.hsqldb/.classpath
new file mode 100644
index 0000000..8804c41
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/.classpath
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry exported="true" kind="lib" path="lib/hsqldb.jar"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/.cvsignore b/plugins/org.eclipse.net4j.db.hsqldb/.cvsignore
new file mode 100644
index 0000000..ba077a4
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/.cvsignore
@@ -0,0 +1 @@
+bin
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/.options b/plugins/org.eclipse.net4j.db.hsqldb/.options
new file mode 100644
index 0000000..9a0c12b
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/.options
@@ -0,0 +1,4 @@
+# Debugging and tracing options
+
+org.eclipse.net4j.db.hsqldb/debug = true
+org.eclipse.net4j.db.hsqldb/debug.sql = true
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/.project b/plugins/org.eclipse.net4j.db.hsqldb/.project
new file mode 100644
index 0000000..1d91938
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/.project
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.net4j.db.hsqldb</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/META-INF/MANIFEST.MF b/plugins/org.eclipse.net4j.db.hsqldb/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..d0b867d
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/META-INF/MANIFEST.MF
@@ -0,0 +1,13 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.net4j.db.hsqldb;singleton:=true
+Bundle-Version: 0.8.0.qualifier
+Bundle-Vendor: %providerName
+Bundle-Localization: fragment
+Bundle-ClassPath: .,
+ lib/hsqldb.jar
+Fragment-Host: org.eclipse.net4j.db;bundle-version="[0.8.0,0.9.0)"
+Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.3.0,4.0.0)"
+Export-Package: org.eclipse.net4j.db.internal.hsqldb;version="0.8.0",
+ org.hsqldb.jdbc;x-friends:="org.eclipse.net4j.tests,org.eclipse.emf.cdo.tests,org.eclipse.net4j.jms.tests"
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/about.html b/plugins/org.eclipse.net4j.db.hsqldb/about.html
new file mode 100644
index 0000000..d35d5ae
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/about.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>June 5, 2007</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;). Unless otherwise
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is available
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was
+provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org/">http://www.eclipse.org</a>.</p>
+
+</body>
+</html>
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/build.properties b/plugins/org.eclipse.net4j.db.hsqldb/build.properties
new file mode 100644
index 0000000..53329fd
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/build.properties
@@ -0,0 +1,24 @@
+# Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# Eike Stepper - initial API and implementation
+
+# NLS_MESSAGEFORMAT_VAR
+
+source.. = src/
+output.. = bin/
+bin.includes = META-INF/,\
+ .,\
+ about.html,\
+ .options,\
+ copyright.txt,\
+ epl-v10.html,\
+ license.html,\
+ fragment.properties,\
+ fragment.xml,\
+ lib/,\
+ lib/hsqldb.jar
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/copyright.txt b/plugins/org.eclipse.net4j.db.hsqldb/copyright.txt
new file mode 100644
index 0000000..025f152
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/copyright.txt
@@ -0,0 +1,8 @@
+Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+All rights reserved. This program and the accompanying materials
+are made available under the terms of the Eclipse Public License v1.0
+which accompanies this distribution, and is available at
+http://www.eclipse.org/legal/epl-v10.html
+
+Contributors:
+ Eike Stepper - initial API and implementation \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/epl-v10.html b/plugins/org.eclipse.net4j.db.hsqldb/epl-v10.html
new file mode 100644
index 0000000..d7b88e9
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/epl-v10.html
@@ -0,0 +1,319 @@
+<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"><head>
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<meta name="ProgId" content="Word.Document">
+<meta name="Generator" content="Microsoft Word 9">
+<meta name="Originator" content="Microsoft Word 9">
+<link rel="File-List" href="http://www.eclipse.org/org/documents/Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml"><title>Eclipse Public License - Version 1.0</title><!--[if gte mso 9]><xml>
+ <o:DocumentProperties>
+ <o:Revision>2</o:Revision>
+ <o:TotalTime>3</o:TotalTime>
+ <o:Created>2004-03-05T23:03:00Z</o:Created>
+ <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
+ <o:Pages>4</o:Pages>
+ <o:Words>1626</o:Words>
+ <o:Characters>9270</o:Characters>
+ <o:Lines>77</o:Lines>
+ <o:Paragraphs>18</o:Paragraphs>
+ <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
+ <o:Version>9.4402</o:Version>
+ </o:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+ <w:TrackRevisions/>
+ </w:WordDocument>
+</xml><![endif]-->
+
+
+<style>
+<!--
+ /* Font Definitions */
+@font-face
+ {font-family:Tahoma;
+ panose-1:2 11 6 4 3 5 4 4 2 4;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:553679495 -2147483648 8 0 66047 0;}
+ /* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {mso-style-parent:"";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p
+ {margin-right:0in;
+ mso-margin-top-alt:auto;
+ mso-margin-bottom-alt:auto;
+ margin-left:0in;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p.BalloonText, li.BalloonText, div.BalloonText
+ {mso-style-name:"Balloon Text";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:8.0pt;
+ font-family:Tahoma;
+ mso-fareast-font-family:"Times New Roman";}
+@page Section1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.25in 1.0in 1.25in;
+ mso-header-margin:.5in;
+ mso-footer-margin:.5in;
+ mso-paper-source:0;}
+div.Section1
+ {page:Section1;}
+-->
+</style></head>
+
+<body style="" lang="EN-US">
+
+<div class="Section1">
+
+<p style="text-align: center;" align="center"><b>Eclipse Public License - v 1.0</b>
+</p>
+
+<p><span style="font-size: 10pt;">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
+THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
+REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
+OF THIS AGREEMENT.</span> </p>
+
+<p><b><span style="font-size: 10pt;">1. DEFINITIONS</span></b> </p>
+
+<p><span style="font-size: 10pt;">"Contribution" means:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and<br clear="left">
+b) in the case of each subsequent Contributor:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+changes to the Program, and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+additions to the Program;</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">where
+such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution 'originates' from a Contributor
+if it was added to the Program by such Contributor itself or anyone acting on
+such Contributor's behalf. Contributions do not include additions to the
+Program which: (i) are separate modules of software distributed in conjunction
+with the Program under their own license agreement, and (ii) are not derivative
+works of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Contributor" means any person or
+entity that distributes the Program.</span> </p>
+
+<p><span style="font-size: 10pt;">"Licensed Patents " mean patent
+claims licensable by a Contributor which are necessarily infringed by the use
+or sale of its Contribution alone or when combined with the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Program" means the Contributions
+distributed in accordance with this Agreement.</span> </p>
+
+<p><span style="font-size: 10pt;">"Recipient" means anyone who
+receives the Program under this Agreement, including all Contributors.</span> </p>
+
+<p><b><span style="font-size: 10pt;">2. GRANT OF RIGHTS</span></b> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+Subject to the terms of this Agreement, each Contributor hereby grants Recipient
+a non-exclusive, worldwide, royalty-free copyright license to<span style="color: red;"> </span>reproduce, prepare derivative works of, publicly
+display, publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and object code
+form.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide,<span style="color: green;"> </span>royalty-free
+patent license under Licensed Patents to make, use, sell, offer to sell, import
+and otherwise transfer the Contribution of such Contributor, if any, in source
+code and object code form. This patent license shall apply to the combination
+of the Contribution and the Program if, at the time the Contribution is added
+by the Contributor, such addition of the Contribution causes such combination
+to be covered by the Licensed Patents. The patent license shall not apply to
+any other combinations which include the Contribution. No hardware per se is
+licensed hereunder. </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">c)
+Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor
+that the Program does not infringe the patent or other intellectual property
+rights of any other entity. Each Contributor disclaims any liability to Recipient
+for claims brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the rights and
+licenses granted hereunder, each Recipient hereby assumes sole responsibility
+to secure any other intellectual property rights needed, if any. For example,
+if a third party patent license is required to allow Recipient to distribute
+the Program, it is Recipient's responsibility to acquire that license before
+distributing the Program.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">d)
+Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in
+this Agreement. </span></p>
+
+<p><b><span style="font-size: 10pt;">3. REQUIREMENTS</span></b> </p>
+
+<p><span style="font-size: 10pt;">A Contributor may choose to distribute the
+Program in object code form under its own license agreement, provided that:</span>
+</p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it complies with the terms and conditions of this Agreement; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+its license agreement:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title
+and non-infringement, and implied warranties or conditions of merchantability
+and fitness for a particular purpose; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such
+as lost profits; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iii)
+states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iv)
+states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a
+medium customarily used for software exchange.<span style="color: blue;"> </span></span></p>
+
+<p><span style="font-size: 10pt;">When the Program is made available in source
+code form:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it must be made available under this Agreement; and </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b) a
+copy of this Agreement must be included with each copy of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Contributors may not remove or alter any
+copyright notices contained within the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Each Contributor must identify itself as the
+originator of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution. </span></p>
+
+<p><b><span style="font-size: 10pt;">4. COMMERCIAL DISTRIBUTION</span></b> </p>
+
+<p><span style="font-size: 10pt;">Commercial distributors of software may
+accept certain responsibilities with respect to end users, business partners
+and the like. While this license is intended to facilitate the commercial use
+of the Program, the Contributor who includes the Program in a commercial
+product offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial
+Contributor") hereby agrees to defend and indemnify every other
+Contributor ("Indemnified Contributor") against any losses, damages and
+costs (collectively "Losses") arising from claims, lawsuits and other
+legal actions brought by a third party against the Indemnified Contributor to
+the extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor
+to control, and cooperate with the Commercial Contributor in, the defense and
+any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.</span> </p>
+
+<p><span style="font-size: 10pt;">For example, a Contributor might include the
+Program in a commercial product offering, Product X. That Contributor is then a
+Commercial Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance claims and
+warranties are such Commercial Contributor's responsibility alone. Under this
+section, the Commercial Contributor would have to defend claims against the
+other Contributors related to those performance claims and warranties, and if a
+court requires any other Contributor to pay any damages as a result, the
+Commercial Contributor must pay those damages.</span> </p>
+
+<p><b><span style="font-size: 10pt;">5. NO WARRANTY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
+WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
+MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and distributing the
+Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or
+equipment, and unavailability or interruption of operations. </span></p>
+
+<p><b><span style="font-size: 10pt;">6. DISCLAIMER OF LIABILITY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
+THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
+
+<p><b><span style="font-size: 10pt;">7. GENERAL</span></b> </p>
+
+<p><span style="font-size: 10pt;">If any provision of this Agreement is invalid
+or unenforceable under applicable law, it shall not affect the validity or
+enforceability of the remainder of the terms of this Agreement, and without
+further action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.</span> </p>
+
+<p><span style="font-size: 10pt;">If Recipient institutes patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Program itself (excluding combinations of the Program with
+other software or hardware) infringes such Recipient's patent(s), then such
+Recipient's rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed. </span></p>
+
+<p><span style="font-size: 10pt;">All Recipient's rights under this Agreement
+shall terminate if it fails to comply with any of the material terms or
+conditions of this Agreement and does not cure such failure in a reasonable
+period of time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use and
+distribution of the Program as soon as reasonably practicable. However,
+Recipient's obligations under this Agreement and any licenses granted by
+Recipient relating to the Program shall continue and survive. </span></p>
+
+<p><span style="font-size: 10pt;">Everyone is permitted to copy and distribute
+copies of this Agreement, but in order to avoid inconsistency the Agreement is
+copyrighted and may only be modified in the following manner. The Agreement
+Steward reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement Steward has
+the right to modify this Agreement. The Eclipse Foundation is the initial
+Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version
+of the Agreement will be given a distinguishing version number. The Program
+(including Contributions) may always be distributed subject to the version of
+the Agreement under which it was received. In addition, after a new version of
+the Agreement is published, Contributor may elect to distribute the Program
+(including its Contributions) under the new version. Except as expressly stated
+in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
+the intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.</span> </p>
+
+<p><span style="font-size: 10pt;">This Agreement is governed by the laws of the
+State of New York and the intellectual property laws of the United States of
+America. No party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each party waives
+its rights to a jury trial in any resulting litigation.</span> </p>
+
+<p class="MsoNormal"><!--[if !supportEmptyParas]-->&nbsp;<!--[endif]--><o:p></o:p></p>
+
+</div>
+
+</body></html> \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/fragment.properties b/plugins/org.eclipse.net4j.db.hsqldb/fragment.properties
new file mode 100644
index 0000000..fe27290
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/fragment.properties
@@ -0,0 +1,25 @@
+# Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# Eike Stepper - initial API and implementation
+
+# NLS_MESSAGEFORMAT_VAR
+
+# ==============================================================================
+# Do not change the properties between this line and the last line containing:
+# %%% END OF TRANSLATED PROPERTIES %%%
+# Instead, either redefine an existing property, or create a new property,
+# append it to the end of the file, and change the code to use the new name.
+# ==============================================================================
+
+pluginName = Net4j DB HSQLDB (Incubation)
+providerName = Eclipse.org
+
+# ==============================================================================
+# %%% END OF TRANSLATED PROPERTIES %%%
+# The above properties have been shipped for translation.
+# ==============================================================================
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/fragment.xml b/plugins/org.eclipse.net4j.db.hsqldb/fragment.xml
new file mode 100644
index 0000000..6c1a4cd
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/fragment.xml
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.3"?>
+<!--
+ <copyright>
+
+ Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ All rights reserved. This program and the accompanying materials
+ are made available under the terms of the Eclipse Public License v1.0
+ which accompanies this distribution, and is available at
+ http://www.eclipse.org/legal/epl-v10.html
+
+ Contributors:
+ Eike Stepper - Initial API and implementation
+
+ </copyright>
+-->
+
+<plugin>
+
+ <extension
+ point="org.eclipse.net4j.db.dbAdapters">
+ <dbAdapter
+ class="org.eclipse.net4j.db.internal.hsqldb.HSQLDBAdapter"
+ name="hsqldb"
+ version="1.8.0.8">
+ </dbAdapter>
+ </extension>
+
+</plugin>
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/.cvsignore b/plugins/org.eclipse.net4j.db.hsqldb/lib/.cvsignore
new file mode 100644
index 0000000..d392f0e
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/.cvsignore
@@ -0,0 +1 @@
+*.jar
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_2.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_2.txt
new file mode 100644
index 0000000..453d63a
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_2.txt
@@ -0,0 +1,813 @@
+Chronological Change List
+
+This file is the accumulated list of changes in the course of development of
+hsqldb 1.7.2 in reverse chronological order. A list of changes by subject
+area is in changelog_1_7_2.txt.
+
+Fred Toussi (fredt@users.sourceforge.net)
+
+2004.12.24 UPDATED RELEASE 1.7.2.11
+
+Fixed NPE error when functions in subqueries.
+Added support for STDDEV_POP, STDDEV_SAMP, VAR_POP, VAR_SAMP, EVERY and SOME set functions.
+Fixed potential issues with logging DELETE statements for tables with multi-key primary keys.
+
+2004.12.05 UPDATED RELEASE 1.7.2.10
+
+Fixed minor type conversion bugs.
+Fixed JDK 1.1 compile issue
+Fixed minor bug relating to server thread startup
+
+2004.11.25 UPDATED RELEASE 1.7.2.8
+
+Fixed bug LIMIT and TOP with UNION
+Fixed bug running Database Manager as applet
+Enhancement to allow a table with a label used in DELETE and UPDATE
+Enhancement to reduce memory use when restoring long log with too many connections
+Enhancement to persist values set by SET LOGSIZE
+Minor internal enhancements and refactoring
+
+2004.10.28 UPDATED RELEASE 1.7.2.7
+
+Fixed new bug with TEXT TABLES without primary key
+
+2004.10.25 UPDATED RELEASE 1.7.2.6
+
+Fixed new bug with DATETIME literal default values
+
+2004.10.22 UPDATED RELEASE 1.7.2.5
+
+Fixed bugs OUTER support.
+Fixed bug that resulted in slowdown when JDBC metadata calls are called many times.
+Fixed bug related to Statement.setMaxRows(int). The maximum row count will no
+longer apply to result sets returned and used internally.
+Fixed bug to allow ResultSetMetaData methods to be used inside stored procedures.
+Fixed bugs related to some OUTER queries.
+Performance improvements to some operations on CACHED tables.
+Improved compatibility with older database files, allowing old style DEFAULT
+clauses to compile.
+Improvements to startup after a machine crash. The .log file is now read only
+until the first malformed line.
+Corrections to build scripts and #idfef blocks to allow jars to be compiled to
+run under JDK 1.1.
+
+
+2004.08.26 UPDATED RELEASE 1.7.2.4
+
+Fixed bug in data file enlargement.
+Fixed bug where temp tables were removed after another connection closed.
+
+2004.08.12 UPDATED RELEASE 1.7.2.3
+
+Fixed bug preventing the use of hsqldb.files_read_only property
+Minor enhancements allowing use of SELECT ALL and COUNT(ALL colname) etc.
+Corrections to the documentation
+
+2004.07.25 UPDATED RELEASE 1.7.2.2
+
+Fixed bug that prevented ALTER TABLE ADD FOREIGH KEY, ADD UNIQUE and ADD CHECK
+(unnamed constraints) from executing.
+
+Fixed excessive logging of SEQUENCE values.
+
+
+2004.07.20 UPDATED RELEASE 1.7.2.1
+
+Fixed bug where a foreign key with ON DELETE CASCADE action on a table masked
+other foreign keys on the table and resulted in completion of the
+cascading action when referential integrity was violated.
+
+2004.07.15 RC_6e INITIAL RELEASE 1.7.2
+
+Enhancements to ALTER TABLE ADD COLUMN and DROP COLUMN.
+Fixed bug with closed HTTP connections.
+Fixed bug with large .data files switching to random access from nio.
+
+2004.06.28 RC_6d
+
+The implemntation of UNION, EXCEPT and INTERSECT set operations has been
+rewritten to comply with SQL standards.
+When multiple set operations are present in a query, they are now evaluated
+from left to right, with INTERSECT taking precedence over the rest.
+It is now possible to use parentheses around multiple (or single) select
+statements with set operations to change the order of evalation.E.g.:
+
+((SELECT * FROM A EXCEPT SELECT * FROM B) INTERSECT SELECT * FROM D UNION SELECT * FROM E)
+
+Timestamp, date and time values in TEXT TABLE source files are treated more
+leniently, allowing spaces before values.
+
+2004.06.19 RC_6c
+
+Fixed bug in default value definition.
+Fixed bug in getURL() for internal connections
+Fixed bug in evaluation of BOOLEAN values
+Fixed bug in Statement.executeBatch()
+Improvements in CHECKPIONT DEFRAG
+Improvements in nio .data file handling
+Added a procedural language to SqlTool. Made error handling and control more
+robust. Implemented several new features.
+Updated documentation
+
+2004.05.31 RC_6b
+
+Fixed CHECKPOINT DEFRAG bug with empty tables
+Fixed ORDER BY with HAVING
+Fixed SELECT .. INTO table issue with outer joins etc.
+Fixed issue with NOT used in WHERE clause of OUTER select
+Fixed issue with DAYOFWEEK() etc. library calls with NULL parameter
+Fixes for TRIGGER thread termination
+Fixes for minor bugs
+Updated documentation
+
+2004.05.18 RC_6a
+
+Fix for two bugs, some doc updates, etc.
+
+2004.05.17 RC_6
+Final Release Candidate
+
+This is the final release candidate for 1.7.2.
+
+More tests are required to verify the improvements. Please perform tests and
+report any issues. Testers are needed for build scripts with different JVM's
+using both ANT and batch builds.
+
+Documentation has been updated and is available in HTML and PDF formats.
+
+More bug fixes to engine and JDBC classes.
+
+Bug fixes and minor enhancements to Database Manager and Transfer tools.
+
+Database Manager Swing table view is sortable.
+
+Fixed bug with different values in one row with multiple CURRENT_TIMESTAMP or
+NOW() calls.
+
+Introduction of CURRENT_USER, can be used as column default value as well.
+
+CURRENT_TIMESTAMP, NOW, TODAY etc. should not be quoted when used as column
+default values.
+
+Improvements to PreparedStatement set stream methods.
+
+Improvements to Clob and Blob implementations.
+
+Much of the UNIX init script redesigned. Now supports TLS and WebServer.
+
+2004.05.01
+
+Small improvements in different areas
+
+CURRENT_TIME, CURRENT_DATE, CURRENT_TIMESTAMP and their aliases can now
+be used in views and prepared statements.
+
+Some bug fixes and updates to utility programs.
+
+Improvements to cascading update operations, allowing full capability with
+FK's referencing the same table.
+Improved parametric INSERT .... SELECT.
+CHECKPOINT DEFRAG now works with nio mode .data files.
+DATEDIFF function has been added.
+
+
+2004.04.01 RC_5
+
+Some bug fixes.
+
+2004.03.22 RC_4
+
+Included hsqldb.jar has been compiled with JDK 1.4 and will not work with JRE 1.3.x or
+earlier. Please recompile with JDK 1.3 for use with this or earlier JDK's.
+
+Improvements to ALTER TABLE when VIEWS reference the table
+Enhancements to Server
+
+Bug fixes for:
+BIGINT values in IN predicate value lists.
+Creation of self ref foreign keys.
+Corrupted log file with SET AUTOCOMMIT
+SET LOGSIZE
+
+
+Bug fixes for LIKE with default local and ALTER TABLE with CHECK
+
+2004.03.13 RC_3
+
+Various bug fixes.
+
+
+2004.02.22 RC_2
+
+Release Candidate 2 for HSQLDB version 1.7.2 includes almost all of the features of the release
+version. It is possible that by the time of the release, a small number of minor features will
+be added or changed.
+
+One area that is likely to change is the SQL_STATE values for errors returned by
+JDBC.
+
+Changes since RC_1
+
+Constraint names must be unique within each database.
+
+Refactoring groups of classes into new packages. This change is internal and does not affect the
+use of hsqldb.
+
+New SqlTool and SqlFile utilities by Blaine Simpson. See hsqlSqlTool.html for details.
+
+Support for new system tables for constraints, views and sequences.
+
+Support for increments in GENERATED BY DEFAULT AS IDENTITY(START WITH <n>, INCREMENT BY <m>>)
+
+Support for table aliases in UPDATE
+
+BOOLEAN is now the default SQL type for boolean values. BIT is treated as an alias
+for BOOLEAN in table definition and queries.
+
+Library function CURTIME() changed to return CURRENT_TIME instead of CURRENT_TIMESTAMP
+
+Added logging for sequence generation
+
+Bug Fixes since RC_1
+
+Values for BOOLEAN expressions containing AND, OR, LIKE and used in columns
+returned by queries are now correct.
+
+Fixed issue with single value selects in UPDATE and SELECT statements.
+
+Fixed issue with Turkish Locale.
+
+Fixed issue with compiled statements.
+
+Added mutable object cloning and serialization on PrepredStatement parameter entry points
+for in-process connections. Isolates the stored objects (DATETIME, BINARY and OTHER) from
+subsequent changes made to the copy used for setting the parameter. To do same for Result.
+
+More extensive error message when internal asserts fail.
+
+Various other bug fixes.
+
+
+2003.12.28 RC_1
+
+Release Candidate 1 for HSQLDB version 1.7.2 includes most of the features of the release
+version. It is likely that by the time of the release, a small number of features will
+be added to the engine.
+
+One area that is likely to change is the SQL_STATE values for errors returned by
+JDBC.
+
+Changes since ALPHA_T
+
+
+Added referential integrity checks when a foreign key is added
+to a populated table.
+
+support for SQL style SEQUENCE objects.
+
+support for DROP INDEX <IDX> IF EXISTS
+
+Changes to SET PROPERTY command with better error checking.
+
+Added support for LIMIT ? ? and TOP ? (prepared statement)
+
+Fixed reported bugs including order by with UNION.
+
+Added support for aggregate functions in CASEWHEN, IFNULL, etc.
+
+Added support for aggregate functions as arguments to non-aggregate functions.
+
+Views and subqueries can appear in a view definition.
+
+
+2003.10.26
+
+HSQLDB 1.7.2 ALPHA_T
+
+Improved index use for multiple key joins.
+
+2003.10.24
+
+Fixed some reported and unreported bugs.
+
+View definitions can now have a column name list:
+
+CREATE VIEW <viewname> [(<colnmae>, ...)] AS SELECT ....
+
+
+2003.10.21
+
+HSQLDB 1.7.2 ALPHA_S
+
+Fixed name resolution issues in some IN (SELECT ...) and EXISTS (SELECT ...)
+queries. Optimisation of these queries when not correlated.
+
+Speed optimisation of joins with views and subqueries.
+
+Fixed LIKE parameter bug.
+
+Support for CHECK constraints that apply to the modified/inserted row only.
+This can be added via ALTER TABLE ADD CHECK() or in table definition.
+
+Fixed the DATETIME normalisation issues.
+Fixed ResultSet.isAfterLast() issue.
+
+Reverted column name case in ResultSet methods to JDBC compliance.
+
+
+2003.10.12
+
+HSQLDB 1.7.2 ALPHA_R
+
+This release features full support for prepared statements with parameters, including
+those in IN lists.
+
+Query processing has been extensively enhanced in this release and better standards
+compliance has been achieved. Major implications of the recent changes are as follows:
+
+- Columns in correlated subqueries are resolved independently first. If there is an
+unresolved column, then the surrounding context is used to resolve it. This is
+opposite the resolution order previously enforced in the engine.
+
+- Some ambiguities and errors in ORDER BY clauses are now caught.
+
+- UNION and other set queries accept only one ORDER BY clause at the end. In this
+clause, only column indexes are allowed as sort specification e.g.:
+
+SELECT .. UNION SELECT .. ORDER BY 1 DESC, 5, 3
+
+- Outer join conditions can now include most comparison operators, as well as OR
+logical operators , e.g
+
+LEFT OUTER JOIN atable ON a=b AND c>d OR a=2 ...
+
+Illegal forward table references are no longer allowed in join conditions.
+
+There are many other small improvements and fixes, including:
+
+- IN value lists can now contain column values or expressions. See TestSelfQueries.txt
+for an example.
+
+- LIKE has been optimised when possible.
+
+- COALESCE() can now take several arguments
+
+
+2003.09.24
+
+HSQLDB 1.7.2 ALPHA_Q
+
+The problem with PreparedStatement parameters in IN lists still remains to be fixed.
+
+This release includes some bug fixes and improvements. In the /doc directory
+there is a new how-to document on using HSQLDB in OpenOffice.org.
+
+
+HSQLDB 1.7.2 ALPHA_P
+
+Apart from the bugs and limitations of PreparedStatement, all the bugs reported since
+the release of ALPHA_O have been fixed in this alpha version. Some minor enhancements
+have been made to increase compatibility with OpenOffice.org applications.
+
+In addition, it is now possible to execute triggers in the main execution thread.
+This allows uses for triggers that were not possible before.
+
+
+HSQLDB 1.7.2 ALPHA_O
+
+Due to the large number of small bug fixes since the release of ALPHA_N,
+a new ALPHA_0 version is now released.
+
+Please see the bug tracker for a list of some of the bugs that have been fixed.
+This version does not yet support prepared statements with IN(?,?) parameters.
+
+Please report any bugs or suggestions through the normal channels. Bugs with test
+cases should be posted to the bug tracker on the HSQLDB Sourceforge site.
+
+A new JDBC connection property "toupper_column_name" can be used when the application
+program submits lowercase / mixedcase column names to Result.getXXX(String column)
+methods when the names are in fact UPPERCASE as they were not quoted when the
+table was created. The default value is false. See related documentation in
+hsqldbAdvancedGuide.html on how to set this property value. (this property was
+subsequently dropped)
+
+The rest of the information for ALPHA_N below applies to this version too.
+
+
+HSQLDB 1.7.2 ALPHA_N
+
+ALPHA_N is the ultimate ALPHA version for the 1.7.2 release cycle. Known
+deficiencies and reported bugs will be addressed for the first Release Candidate
+to be issued in the next few weeks.
+
+Please report any bugs or suggestions through the normal channels. Bugs with test
+cases should be posted to the bug tracker on the HSQLDB Sourceforge site.
+
+The included documentation has been updated. The JavaDoc for the jdbcXXX classes
+covers the JDBC interface. You can make the JavaDoc via the build scripts.
+
+The jar has been compiled with JDK 1.4. To run under earlier JDK's recompile using
+JDK 1.3.x.
+
+Changes since 1.7.2 are listed here in the reverse chronological order.
+
+2003.09.02
+
+ADDED JDBC SUPPORT FOR SAVPOINTS
+
+2003.08.22
+
+FURTHER SPEED IMPROVEMENTS IN ALL LOGGED MODES
+INSERT and UPDATE ops are faster by 5-20% in MEMORY tables, less in CACHED tables.
+
+
+ADDED SUPPORT FOR A RANGE OF SQL STYLE FUNCTIONS:
+
+CASE .. WHEN ... THEN .. ELSE ... END
+CASE WHEN .. THEN .. ELSE ... END
+NULLIF(.. , ..)
+SUBSTRING(.. FROM .. FOR ..)
+POSITION(.. IN ..)
+TRIM( {LEADING | TRAILING .. } FROM ..)
+EXTRACT({DAY | TIME |..} FROM ..)
+COALESCE(.. , ..)
+
+
+2003.08.17
+
+FURTHER IMPROVEMENTS IN PREPARED STATEMENT EXECUTION SPEED
+
+SUPPORT FOR JDBC BATCH EXECUTION
+
+SUPPORT FOR MULTIPLE ROWS WITH NULL FIELDS UNDER UNIQUE CONSTRAINTS
+
+IMPROVEMENTS TO TestSelf
+
+IMPROVEMENTS TO ON UPDATE CASCADE / SET DEFAULT / SET NULL
+
+2003.08.11
+
+REWRITE OF LEFT OUTER JOIN SUPPORT
+
+- Complete rewrite of join processing abolishes the requirement for
+an index on any joined columns. All expressions with AND are supported
+in the join condition (JOIN atable ON ....)
+
+IMPROVEMENTS TO ON DELETE CASCADE / SET DEFAULT / SET NULL
+
+- Self referencing foreign keys and multiple foreign keys now support
+ON DELETE CASCADE.
+
+2003.08.02
+
+NIO ACCESS FOR .data FILES
+
+New nio access layer for .data files speeds up most CACHED TABLE related
+operations very significantly. 90% speedups in TestCacheSize tests
+have been observed. The program must be compiled with JDK 1.4 and run
+in a 1.4 JRE to use the new access mode.
+
+IMPROVEMENTS TO UPDATE AND INSERT
+
+Certain types of UPDATES and INSERTS that previously failed due to
+blanket application of UNIQUE constraints now work.
+
+Examples include UPDATE ... SET col = col + 1 where col is an identity
+column or INSERT a self referencing row under FOREIGN key constraints.
+
+2003.07.30
+
+IMPORTANT FIX IN SELECT QUERY PROCESSING
+
+Problems with OUTER and INNER joins returning incorrect results
+have been reported over the last couple of years. A new fix is
+intended to ensure correct results in all cases.
+
+- When two tables are joined, rows resulting from joining null
+values in the joined columns are no longer returned.
+
+- Use of OUTER requires the existence of an index on a joined OUTER column
+- There are still limitations on the conditions used in OUTER joins.
+
+AGGREGATES
+
+- enhancements to aggregate functions: aggregates of different numeric
+types are now supported
+
+SUM returns a BIGINT for TINYINT, SMALLINT and INTEGER columns. It
+returns a DECIMAL for BIGINT columns (scale 0) and DECIMAL columns
+scale equals to that of the column).
+
+AVG returns the same type as the column or the expression in its
+argument.
+
+- aggregates with GROUP BY do not return any rows if table is empty
+
+OLDER ENHANCEMENTS NOT PREVIOUSLY REPORTED
+
+- IDENTITY columns can now be of BIGINT type:
+
+CREATE TABLE <name> (<column> BIGINT IDENTITY, ...)
+
+- With contributed patch, TEXT TABLES encoding of the source file can
+now be specified. UTF-8 and other encodings can be used.
+
+- Two new options for databases: files_readonly and files_in_jar
+were added based on submitted patches.
+
+FILE READ-ONLY
+
+If the property files_readonly=true is set in the database
+.properties file, no attempt is made to write the changes to data to
+file. Default, memory tables can be read/write but TEXT and CACHED
+tables are treated as read-only.
+
+FILES IN JAR
+
+This option allows database files to be distributed in the
+application jar. We have changed the original contribution so
+that a special URL is used for this mode in the form of:
+
+jdbc:hsqldb:res:<path in jar>
+
+The URL type 'res' determines that the path that follows is a path
+into the JAR.
+
+The database can be readonly or files_readonly, depending on the
+value set in .properties file.
+
+2003.07.09
+
+SCRIPT FORMAT
+
+- change to command previously named SET LOGTYPE (discussed below for
+earlier alphas) new form is:
+SET SCRIPTFORMAT {TEXT | BINARY | COMPRESSED }
+
+The new binary and compressed formats are not compatible with previous
+ones, so you should change any old 1.7.2 ALPHA_? database to text
+mode with SET LOGTYPE 0 before opening with the new version.
+
+'OTHER' DATA TYPE
+
+- change to handling of OTHER columns. It is no longer required that
+the classes for objects stored in OTHER columns to be available on
+the path of an HSQLDB engine running as a server. Classes must be
+available on the JDBC client's path.
+
+OBJECT POOLING
+
+- the new Object pool has been incorporated. This reduces memory
+usage to varying degrees depending on the contents of database
+tables and speeds up the database in most cases. Currently the
+size of the pool is hard-coded but it will be user adjustable in the
+release version.
+
+CONNECTION PROPERTY
+
+- a new property, ifexists={true|false} can be specified for connections.
+It has an effect only on connections to in-process databases. The default
+is false and corresponds to current behaviour.
+
+If set true, the connection is opened only if
+the database files have already been created -- otherwise no new database
+is created and the connection attempt will fail. Example:
+
+jdbc:hsqldb:hsql:mydb;ifexists=true
+
+This property is intended to reduce problems resulting from wrong URL's
+which get translated to unintended new database files. It is recommended
+to use this property for troubleshooting.
+
+2003.07.04
+
+PREPARED STATEMENTS
+
+- support for real PreparedStatements - major speedup. Current limitations
+include lack of support for parameters in IN() predicates of queries.
+
+TRANSACTIONS VIA WEB SERVER
+
+- uniform support for transactions via HSQL and HTTP (WebServer and Servlet)
+protocols
+
+MULTIPLE IN-MEMORY AND SERVERS DATABASES
+
+- support for multiple memory-only databases within the same JVM
+
+- support for simultaneous multiple servers, multiple internal
+connections and multiple databases within the same JVM
+
+
+NEW CONVENTIONS FOR URL'S AND .properties FILES
+
+Each HSQLDB server or webserver can now serve up to 10 different databases.
+
+The server.properties and webserver.properties method for defining the
+databases has changed. The following properties should be used:
+
+server.database.0 path_of_the_first_database
+server.dbname.0 alias_for_the_first_database
+
+Up to 10 databases can be defined but they must start from 0
+
+The same applies to command line arguments for Server and WebServer.
+
+The urls for connecting to servers should have the alias of the database
+at the end.
+
+For example, to connect to the HSQL protocol server on the localhost use:
+
+jdbc:hsqldb:hsql://localhost/alias_for_the_database
+
+where alias_for_the_database is the same string as defined in
+server.properties as server.dbnam.n
+
+The default for server.dbname.0 is "" (empty string) so that
+old URL types continue to work.
+
+Multiple memory-only database are supported by the use of:
+
+jdbc:hsqldb:mem:alias_for_the_first_database
+jdbc:hsqldb:mem:alias_for_the_second_database
+
+Examples: jdbc:hsqldb:mem:db1 jdbc:hsqldb:mem:mydb
+
+The conneciton type, 'file', can be used for file database
+connections. example below:
+
+jdbc:hsqldb:hsql:file:mydb;ifexists=true
+
+
+The URL for connecting to a Servlet HTTP server must have a
+forward-slash at the end. Servlet serves only one database.
+
+jdbc:hsqldb:hsql://localhost:8080/servlet/HsqlServlet/
+
+
+
+2003.03.10
+
+DATABASE METADATA
+
+-system table support and java.sql.DatabaseMetadate results have been
+overhauled by Campbell.
+
+STRICT FOREIGN KEYS
+
+-strict treatment of foreign key index requirements is now enforced.
+A foreign key declaration _requires_ a unique constraint or index to exist
+on the columns of the referenced table. This applies both to old and
+new databases. Duplicate foreign keys (with exactly the same column sets)
+are now disallowed.
+
+TEXT TABLES
+
+-further improvements to TEXT table support. Smaller cache sizes are
+now the default and the default properties can be specified in the
+*.properties file.
+
+
+
+HSQLDB 1.7.2 ALPHA_M
+
+2003.01.23
+
+-fixed reported bugs in SHUTDOWN COMPACT
+-fixed reported bugs in GRANT statements on system tables
+-fixed bug that prevented UPDATE in some circumstances
+
+some enhancements that appeared in previous versions but not reported:
+
+-enhanced handling of DATE objects - comparability and normalisation
+-support for CLOB methods in ResultSet
+-fixed bug in afterLast() followed by previous() in ResultSet
+
+
+HSQLDB 1.7.2 ALPHA_L
+
+2003.01.16
+
+various patches and fixes
+
+-fixes new issues reported with ALPHA_K
+-fixes old issues related to uncommitted transactions in
+abnormal shutdown
+-fixes old issues with SAVEPOINT names
+-enhanced TEXT table handling and reporting of errors in
+CSV (source) files
+
+
+HSQLDB 1.7.2 ALPHA_K
+
+2003.01.10
+
+various patches and fixes
+
+-OUTER with multiple column joins is now supported while OR is
+disallowed in the join expression. It is now possible to specify
+a range or equality condition on the OUTER columns returned.
+
+-submitted patch for exclusion of NULL values from results of
+range queries has been applied. e.g.
+WHERE columnvalue < 3
+will exclude from the result all rows with NULL in columnvalue.
+
+-a number of small enhancements and bug fixes.
+
+further enhancements to logging.
+-The *.script file now contains only the DDL and data that is
+written at CHECKPOINT or SHUTDOWN.
+The statements logged while the engine is running are stored
+in a *.log file.
+-The format of the *.script file can now be one of TEXT,
+BINARY or COMPRESSED. The SET LOGTYPE {0|1|3} will reset the
+format. A checkpoint is performed at this point if the format
+is different from the existing one.
+The COMPRESSED format has the side benefit of hiding the DDL
+and the admin password.
+-The behaviour of SET WRITE_DELAY has changed with the
+introduction of the sync() method to force the log to be
+written out completely to disk at given intervals.
+SET WRITE_DELAY {TRUE | FALSE} is interpreted as synch every
+60 seconds or 1 second. SET WRITE_DELAY <n> where n is an integer
+is interpreted as synch every n seconds. The current default is
+60 seconds which seems to provide the right balance. The
+performance impact of SET WRITE_DELAY 1 is probably about 15% over that
+of SET WRITE_DELAY 300.
+
+-The recovery from crash has been modified so that any line in the log
+that is not properly written (and causes an error) ends the redo process.
+A message is reported to the user, instead of stopping engine operation.
+
+HSQLDB 1.7.2 ALPHA_J
+
+2002.12.24
+CVS hsqldb-dev module tag: HSQLDB_1_7_2_ALPHA_J
+
+-More work on text tables. See hsqlTextTables.html.
+-Some refactoring of Table.java and Parser.java
+
+
+HSQLDB 1.7.2 ALPHA_I
+
+2002.12.16
+CVS hsqldb-dev module tag: HSQLDB_1_7_2_ALPHA_I
+
+More work on core classes to consolidate previous changes
+-correction of reported bug with text tables and primary keys
+-reducing data file writes esp. with big rows
+-preventing Cache related error in ON DELETE CASCADE
+
+
+HSQLDB 1.7.2 ALPHA_H
+
+2002.12.11
+CVS hsqldb-dev module tag: HSQLDB_1_7_2_ALPHA_H
+
+
+Reduction in JDK / JRE dependencies (see readmebuild.txt)
+Extensive refactoring of some of the larger classes.
+More changes to core classes Node, Row, Index, Cache, Log ...
+Some minor bug fixes and enhancements.
+Enhancements to text table support, including binary columns.
+Bug fixes to User.java and UserManager.java.
+Support for ON UPDATE / DELETE SET NULL / SET DEFAULT
+SSL support for Server mode operation.
+
+2002.10.30
+
+HSQLDB 1.7.2 ALPHA_G
+
+CVS hsqldb-dev module tag: HEAD data: 2002.10.30
+
+New features include:
+
+Tony Lai's enhancements to aggratates and support for HAVING.
+
+Tony's new UnifiedTable class (provisional name) which he kindly wrote
+at my request and provides sorted arrays with minimal storage
+requirements.
+
+My refactoring work on DatabaseRowInput/Output subclasses and Cache.java.
+
+This is still ongoing and has several features aimed at a more robust
+database engine, including:
+- reduction in object creation;
+- possibility of resizing the cache while the engine is running;
+- possibility of exporting and backing up the DB files while the engine is
+ running.
+
+I have implemented the new feature, CHECKPOINT DEFRAG to defragment a
+*.data file without shutting down the engine, in two different versions,
+taking advantage of the above improvements.
+
+I have implemented binary logging of MEMORY table inserts in the *.script
+file, resulting in much smaller startup and shutdown times with large
+memory tables. Use SET LOGTYPE {0|1} to set the log type to text (0) or
+binary (1). This performs a checkpoint if the type needs changing.
+
+Also further performance optimisations resulting in faster CACHED table
+operations have been made.
+
+Sebastian has implemented ON UPDATE CASCADE support for foreign keys. \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_3.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_3.txt
new file mode 100644
index 0000000..7c91d92
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_7_3.txt
@@ -0,0 +1,45 @@
+Chronological Change List
+
+This file is the accumulated list of changes in the course of development of
+hsqldb 1.7.3 in reverse chronological order.
+
+Fred Toussi (fredt@users.sourceforge.net)
+
+2004.02.23 1.7.3.4
+
+Fixed NPE when defining self referencing FK's with no primary key
+
+2004.02.07 1.7.3.3
+
+Fixed bug with loggin of deletes / updates from tables without primary keys. If the a row
+from such tables contained a null value and was deleted / updated, the operation was not
+logged correctly. Subsequently, if there was an abnormal termination after such changes and
+the database was restarted, the logged delete statement would not have any effect and result
+in duplicate rows. This bug did not affect tables with primary keys or the normal operation
+(without abnormal termination) of other tables.
+
+
+2004.01.31 1.7.3.2
+
+Allow conversion from BIGINT to SAMMLINT and TYNYINT (all other legal conversions worked fine)
+Fixed issue with null values in calls to ResultSet methods with a Calendar
+argument.
+Enhancement to allow INSERT INTO <T> SELECT (....) where no column list
+list for the table T is specified.
+
+2004.12.24 1.7.3.1
+
+Corrected scripting of CHECK constraints with NOT NULL and IS NULL
+Fixed NPE error when functions in subqueries.
+Added support for STDDEV_POP, STDDEV_SAMP, VAR_POP, VAR_SAMP, EVERY and SOME set functions.
+Fixed potential issues with logging DELETE statements for tables with multi-key primary keys.
+
+Apart from the BOOLEAN type, 1.7.3.1 is identical to 1.7.2.11
+
+2004.12.05 First release 1.7.3.0
+
+Changed handling of the BOOLEAN type to allow the undefined state.
+This involves changes to the behariour of NOT and NULL, and also CHECK conditions,
+regarding NULL values.
+
+In all other respects, 1.7.3.0 is identical to 1.7.2.10 \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_8_0.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_8_0.txt
new file mode 100644
index 0000000..4391900
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelist_1_8_0.txt
@@ -0,0 +1,529 @@
+Chronological Change List
+
+This file is the accumulated list of changes in the course of development of
+hsqldb 1.8.0, including point releases, in reverse chronological order.
+
+Fred Toussi (fredt@users.sourceforge.net)
+Maintainer, HSQLDB Project
+
+2007.09.06 1.8.0.8.1
+
+Fixed regression that impacted performance of system table selects and JDBC
+DatabaseMetaData calls that use system tables.
+
+2007.08.28 1.8.0.8
+
+Fixed issue with some text table sources.
+Fixed issue caused after adding columns to tables used in certain view definitions
+Added sych call before closing .script files.
+Minor bug fixes
+
+New implementation of HsqlTimer to allow proper database shutdown while used
+within an application server or similar.
+
+Improvements in TEXT TABLE source file handling. If source file is unavailable at
+startup, the source specification is retained but its usage is turned off.
+An SQL warning is added to the first session in the event.
+Added SET TABLE <tablename> SOURCE {ON | OFF} enables/disables the usage of the
+source file.
+
+Some relaxation of use of LIMIT in subqueries
+
+Improvements to SqlTool and DatabaseManager tools by Blaine Simpson.
+
+2006.09.27 1.8.0.7
+
+Fixed regression in 1.8.0.6 that prevented reuse of empty spaces in the .data file.
+Fixed regression that prevented setting the textdb.allow_full_path property
+
+2006.09.22 1.8.0.6
+
+Fixed issue where missing dbname.0 in server properties files was not ignored
+Fixed issue where a crash during logging of an update query may result in
+incomplete logging and recovery
+Fixed issue where a PK defined after another constraint would result in wrong
+constraint name
+Fixed issue with incorrect evaluation of null values in CASE WHEN in certain cases
+Fixed issue where ResultSet column class names were misreported for functions
+returning primitive types
+
+2006.07.27 1.8.0.5
+
+(3 fixed issues affecting durability)
+Fixed serious reported issue in some JVM's zip libraries by adding a workaround.
+Fixed serious issue when cache_scale and cache_size_scale are small but very
+large rows are inserted in cached tables.
+Fixed bug where an automatic rollback of an UPDATE statement was not logged.
+
+Fixed bug with nested JDBC escapes.
+Fixed bug with logging of schema definition.
+Fixed bug where DROP TABLE was allowed even when a view used the table.
+Fixed bug where DISTINCT together with some GROUP BY lists were not allowed.
+Fixed bug where Server.shutdown() threw spurious NPE.
+
+Improved .data file persistence classes with better errror logging.
+
+Improved client/server retrieval speed of large result sets.
+Column declarations of TIME(0) are now accepted.
+Named parameter in the form of :name are allowed in prepared statements.
+
+2006.04.16 1.8.0.4
+
+General improvements to all utilities, including SQLTool, DatabaseManager, etc.
+General improvements to build.xml.
+Improvement to fail-safe persistence by saving the .properties file first as a
+new file, before renaming.
+Fixed bugs with text tables that use quoted source files and have a heading row.
+Fixed bug which prevented dropping a column before an indexed column.
+Fixed bug where DISTINCT was not allowed with SQL functions (BT 1400344)
+Fixed bug where PreparedStatement calls were allowed with some unbound variable
+(Bug Tracker 1399324) but commented out to allow compatibility with earlier
+versions (see org.hsqldb.jdbc.jdbcPreparedStatement).
+VARCHAR_IGNORECASE size specification is now enforeced.
+Fixed bugs where ORDER BY did not work in some cases (BT 1383218, BT 1344895).
+Fixed bug where IFNULL was used with a function (BT 1315834).
+Fixed bug where creation of a new table was not allowed if the old table with
+the same name had been renamed.
+Fixed bug where SYSTEM_INDEXINFO could not be read.
+Fixed bug to allow running with JDK 1.1 when compiled for this target.
+Fixed bug with COALESCE, et containing an aggregate function (BT 1242448).
+
+Fixed bug with ResultSet.getTimestamp(int, Clandar).
+Fixed bug with access non-admin access to tables was allowed when using
+PreparedStatement objects.
+Added org.hsqldb.Library function, getDatabaseFullProductVersion to return the
+full version string, including the 4th digit (e.g 1.8.0.4).
+
+2006.01.08
+
+Fixed bug in WebServer
+Added support for remote startup of databases in Server and WebServer
+
+2005.12.22
+
+Fixed bug where ON DELETE SET DEFAULT was accepted without a matching DEFAULT value
+Fixed bug where column renaming was allowed in tables accessed in views
+Fixed bug where TRUE or FALSE is used as search condition as WHERE .. AND FALSE
+Fixed bug where dropping TEMPORARY tables was not logged
+Fixed bug where negative values for IDENTITY columns were treated as positive
+
+
+2005.11.02 1.8.0.3
+
+Bug fixes
+
+Fixed bug with tables formed with SELECT .. INTO that did not allow creation of indexes
+Fixed bug with scripting of some VIEW definitions with quoted column names
+Fixed bug in generation of some system tables with multi schema databases
+Fixed bug with access to network result set data when UNION with different column
+types is used
+Fixed bug with scripting of some TIMESTAMP values
+
+2005.08.18 1.8.0.2
+
+Bug fixes and enhancements:
+
+Fixed bugs with GLOBAL TEMPORARY tables with PRESERVE ROWS or
+DELETE ROWS options.
+Fixed bug with DESC ignored in ORDER BY when a correlation name was used to
+specify the column.
+Fixed ResultSet.getTimestamp() and PreparedStatement.setTimestam() bug with null
+timestamp parameters.
+Enhancement to allow string contatenation in LIKE predicates.
+Fixed two JDK 1.1.x incompatibilities.
+Fixed issue with some SET TABLE <name> SOURCE <source> command.
+Fixed issue with DDL not being logged immediatedly with WRITE_DELAY set to 0.
+Fixed issue with the combination of CASE WHEN (or COALESCE, etc.) with
+aggregate functions when the table contains no rows and the aggregate function
+returns null.
+Fixed issue with ALTER SCHEMA <name> RENAME TO <name>
+
+New features
+
+Support for RIGHT OUTER JOIN and CROSS JOIN in select statements
+
+ALTER TABLE <name> ALTER COLUMN <name> SET [NOT] NULL
+
+Added DAY_OF_WEEK as an alternative for EXTRACT(XXX FROM <date time>)
+
+
+2005.07.11 1.8.0.1
+
+Bug fixes and enhancements:
+
+Correlated subqueries with UNION (and other set operators) are allowed.
+LEFT OUTER JOIN join statement can contain NOT expressions.
+Set functions, SOME() and EVERY() implementation corrected.
+Quoted empty strings in TEXT table sources are no-longer interpreted as null.
+CHECKPOINT DEFRAG issued while there are uncommitted transactions works correctly.
+build.xml updated to fix issue with JDK 1.3 build
+
+2005.07.01 1.8.0.0
+
+First release.
+
+2005.06.16 1.8.0.RC12
+
+Introduced new connection property shutdown, which, if true on the first
+connection, will cause the engine to perform a SHUTDOWN on the database when
+the last connection is closed.
+
+Enhancements to TEXT table implementation to maintain the commit status of rows
+during recovery from an abrupt shutdown. Uncommitted rows will not appear in
+TEXT tables.
+
+2005.05.17 1.8.0.RC10
+
+SCHEMAS
+
+Support for SQL schemas. Each database can contain multiple schemas. The
+following commands have been introduced:
+
+CREATE SCHMEA <schemaname> AUTHORIZATION DBA
+DROP SCHEMA <schemaname> {CASCADE | RESTRICT}
+ALTER SCHEMA <schemaname> RENAME TO <newname>
+SET SCHEMA <schemaname>
+
+Initially, the default user schema will be created with the name PUBLIC. This
+schema can be renamed or dropped. When the last user schema has been dropped,
+an empty default schema with the name PUBLIC is created.
+
+System tables all belong to INFORMATION_SCHEMA. To access system tables, either
+SET SCHEMA INFORMATION_SCHEMA should be used once or they should be referred to
+by fully specified names, e.g.
+INFORMATION_SCHEMA.SYSTEM_TABLES
+
+Similarly all database objects apart from columns can be referenced with fully
+qualified schema names.
+
+The CREATE SCHEMA command can be followed by other CREATE and GRANT commands
+without an intervening semicolon. All such commands are executed in the context
+of the newly created schema. A semicolon terminates an extended CREATE SCHEMA
+command.
+
+ROLES
+
+Support for SQL standard roles.
+
+CREATE ROLE <role name>
+GRANT ... TO <role name>
+REVOKE ... FROM <role name>
+GRANT <role name> TO <user name>
+DROP ROLE <role name>
+
+The GRANT and REVOKE commands are similar to those used for granting
+permissions on different objects to USER objects. A role can then be granted to
+or revoked from different users, simplifying permission management.
+
+GLOBAL TEMPORARY TABLES
+
+The implementation of temporary tables has changed to conform to SQL standards.
+
+The definition of a GLOBAL TEMPORARY table persists with the database. When a
+session (JDBC Connection) is started, an empty instance of the table is created.
+Temporary tables can be created with (the default) ON COMMIT DELETE ROWS or
+ON COMMIT PRESERVE ROWS added to the end of table definition.
+With ON COMMIT PRESERVE ROWS, the table contents are not cleared when the
+session commits. In both cases, the contents are cleared when the session is
+closed.
+
+
+SCHEMA MANIPULATION COMMANDS
+
+Several schema manipulation commands have been enhanced.
+
+Tables, views and sequences can be dropped with the CASCADE option. This
+silently drops all tables and views that reference the given database object.
+
+DROP TABLE <table name> [IF EXISTS] [CASCADE];
+DROP VIEW <view name> [IF EXISTS] [CASCADE];
+DROP SEQUENCE <sequence name> [IF EXISTS] [CASCADE];
+
+ALTER TABLE <table name> DROP COLUMN now silently drops any primary key or
+unique constraint declared on the column (excluding multi-column constraints).
+
+ALTER TABLE <table name> ADD [COLUMN] now accepts primary key and identity
+attributes.
+
+COLUMN MANIPULATION
+
+Support for converting type, nullability and identity attributes of a column
+
+ALTER TABLE <table name> ALTER COLUMN <column name> <column definition>
+
+<column definition> has the same syntax as normal column definition. The new
+column definition replaces the old one, so it is possible to add/remove a
+DEFAULT expression, a NOT NULL constraint, or an IDENTITY definition.
+No change to the primary key is allowed with this command.
+
+- The column must be already be a PK column to accept an IDENTITY definition.
+- If the column is already an IDENTITY column and there is no IDENTITY
+definition, the existing IDENTITY attribute is removed.
+- The default expression will be that of the new definition, meaning an
+existing default can be dropped by ommission, or a new default added.
+- The NOT NULL attribute will be that of the new definition, similar to above.
+- Depending on the conversion type, the table may have to be empty for the
+command to work. It always works when the conversion is possible in general and
+the individual existing values can all be converted.
+
+A different syntax can be used to change the next value for an IDENTITY column:
+
+ALTER TABLE <table name> ALTER [COLUMN] <column name> RESTART WITH <n>
+
+
+ALL and ANY expressions
+
+Full support for ALL(SELECT ....) and ANY(SELECT ....) with comparison o
+perators: =, >, <, <>, >=, <=
+Example:
+
+SELECT ... WHERE <value expression> >= ALL(SELECT ...)
+
+LIMIT and OFFSET
+
+New alternative syntax for LIMIT at the end of the query:
+
+LIMIT L [OFFSET O]
+
+It is now possible to use LIMIT combined with ORDER BY in subqueries and SELECT
+statements in brackets that are terms of UNION or other set operations.
+
+An ORDER BY or LIMIT clause applies to the complete result of the UNION and
+other set operations or alternatively to one of its components depending on how
+parentheses are used. In the first example the scope is the second SELECT,
+while in the second query, the scope is the result of the UNION.
+
+SELECT ... FROM ... UNION
+(SELECT ... FROM ... ORDER BY .. LIMIT)
+
+SELECT ... FROM ... UNION
+SELECT ... FROM ... ORDER BY .. LIMIT
+
+Support for ORDER BY, LIMIT and OFFSET in CREATE VIEW statements
+
+
+COLLATIONS
+
+Added support for collations. Each database can have its own collation. The SQL
+command below sets the collation from the set of collations in the source
+for org.hsqldb.Collation:
+
+SET DATABASE COLLATION <double quoted collation name>
+
+Once this command has been issued, the database can be opened in any JVM and
+will retain its collation.
+
+The property sql.compare_in_locale=true is no longer supported. If the line
+exists in a .properties file, it will switch the database to the collation for
+the current default.
+
+ENHANCEMENTS
+
+Support for the res: connection protocol (database files in a jar) has been
+extended to allow CACHED tables.
+
+Support for correct casting of TIME into TIMESTAMP, using CURRENT_DATE
+
+Symmetrical handling of setTimestamp() and getTimestamp() with Calendar
+parameters.
+
+BUG FIX
+
+Fixed bug where two indexes where switched, causing wrong results in some
+queries in the following circumstances:
+
+CREATE TABLE is executed.
+ALTER TABLE ADD FORIEGN KEY is used to create an FK on a different table that
+was already present when the first command was issued.
+CREATE INDEX is used to add an index.
+Data is added to the table.
+Database is shutdown.
+Database is restarted.
+At this point the indexes are switched and queries that use either of the
+indexes will not return the correct set of rows.
+
+BUG FIXES
+
+Fixed reported bug with NOT LIKE and null values
+
+Fixed bug with OR conditions in OUTER JOIN
+
+Fixed bug with duplicated closing of prepared statements
+
+Fixed bug with scalar subqueries. If the result of a scalar subquery is empty
+(no rows returned), the value is NULL.
+
+Fixed various parsing anomalies where SQL commands were accepted when quoted,
+double-quoted or prefixed with an identifier, or identifiers were accepted in
+single quotes. Example of a command that is no-longer tolerated:
+
+Malformed query: MY. "SELECT" ID FROM 'CUSTOMER' IF.WHERE ID=0;
+Actual query: SELECT ID FROM CUSTOMER WHERE ID=0;
+
+Fixed bug that prevented adding a primary key with no name to a table.
+
+Fixed bug that resulted in an error when the type of a column was changed to
+the same type as before. E.g.
+ALTER TABLE <table name> ALTER COLUMN <column name> INTEGER
+
+BUG FIX
+
+Fixed bug in ROLLBACK. If several updates were made to a row of a table that
+has no primary key, then ROLLBACK was issued, there would remain multiple
+versions of the row. E.g.
+
+CREATE TABLE T (I INT);
+INSERT INTO T VALUES (0);
+SET AUTOCOMMIT FALSE;
+UPDATE T SET I=1 WHERE I = 0;
+UPDATE T SET I=2 WHERE I = 1;
+UPDATE T SET I=3 WHERE I = 2;
+UPDATE T SET I=4 WHERE I = 3;
+ROLLBACK
+
+After the rollback the table would contain more than one row.
+
+
+2005.03.02 1.8.0.RC9
+
+Fixed unreported bug in recovery when first column contains null.
+Fixed unreported issue with possible PK and FK name duplication
+Fixed reported bug in recovery when there is no primary key.
+Fixed reported issue with deleting self referencing row (with foreign key).
+Fixed reported issue with illegal user names
+Fixed jdk 1.3 compilation issues
+Applied submitted patch to Server
+
+Applied submitted patch for setting the default table type when CREATE TABLE is
+used. The connection property, hsqldb.default_table_type=cached will set the
+default to CACHED tables, or the SET PROPERTY command can be used. Values,
+"cached" and "memory" are allowed.
+
+The database property sql.enforce_strict_size=true has now a wider effect
+Previously CHAR /VARCHAR lengths could be checked and padding performed only
+when inserting / updating rows. Added support for CHAR(n), VARCHAR(n),
+NUMERIC(p,s) and DECIMAL(p,s) including SQL standard cast and convert semantics.
+Explicit CAST(c AS VARCHAR(2)) will always truncate the string. Explicit
+CAST(n AS NUMERIC(p,s)) will always perform the conversion or throw if n is out
+of bounds. All other implicit and explicit conversions to CHAR(n) and VARCHAR(n)
+are subject to SQL standard rules.
+
+Bob has improved support for text tables. Newline support in quoted fields is
+now complete. It is now possible to save and restore the first line header of a
+CSV file when ignore_first=true is specified. When a text table is created with
+a new source (CSV) file, and ignore_first=true has been specified the following
+command can be used to set a user defined string as the first line:
+SET TABLE <tablename> SOURCE HEADER <double quoted string>.
+
+When embedded in OOo, several defaults and properties are set automatically:
+
+CREATE TABLE ... defaults to CREATE CACHED TABLE ...
+hsqldb.cache_scale=13
+hsqldb.cache_size_scale=8
+hsqldb.log_size=10
+SET WRITE DELAY 2
+sql.enforce_strict_size=true
+hsqldb.first_identity=1
+
+
+2005.02.11 1.8.0.RC8
+
+Fixed minor bugs
+
+Added public shutdown() method to Server.
+
+A new application log has been introduced as an optional feature. The
+property/value pair "hsqldb.applog=1" can be used in the first connection string
+to log some important messages. The default is "hsqldb.applog=0", meaning no
+logging. A file with the ending ".app.log" is generated alongside the rest of
+the database files for this purpose.
+
+In the current version only the classes used for file persistence (different in
+OpenOffice.org), plus any error encountered while processing the .log file after
+an abnormal end is logged.
+
+Bob Preston has updated the text table support to accept new line characters
+inside quoted strings. It is still not possible to create / modify a row
+containing a new line inside the engine. This will be a simple upgrade and will
+be included in the next RC.
+
+Note that the JDBC driver and the engine for 1.8.0 cannot be mixed with those of
+earlier versions in client/server setup. Check your classpaths and use the same
+version of the engine for both client and server.
+
+
+2005.01.28 1.8.0.RC7
+
+Fixed minor bugs
+
+2005.01.24 1.8.0.RC5
+
+Issues with SET CHECKPOINT DEFRAG fixed
+
+New property for larger data file limits is introduced. Once set, the limit will
+go up to 8GB. The property can be set with the following SQL command only when
+the database has no tables (new database).
+
+SET PROPERTY "hsqldb.cache_file_scale" 8
+
+To apply the change to an existing database, SHUTDOWN SCRIPT should be performed
+first, then the property=value line below should be added to the .properties
+file before reopening the database:
+
+hsqldb.cache_file_scale=8
+
+It is now possible to add or drop a primary key.
+
+An existing primary key that is to be removed should not be referenced in a
+FOREIGN KEY constraint. If a table has an IDENTITY column, removing a primary
+key will remove the identity attribute of the column but leave the actual data.
+
+When adding a primary key, a NOT NULL constraint is automatically added to the
+column definitions. The table data for the columns of a newly declared primary
+key should not contain null values.
+
+ALTER TABLE <name> ADD CONSTRAINT <cname> PRIMARY KEY(collist);
+ALTER TABLE <name> DROP CONSTRAINT <cname>;
+ALTER TABLE <name> DROP PRIMARY KEY; // alternative syntax
+
+2005.01.20 1.8.0.RC4
+
+More minor bug fixes
+ResultSetMetaData reports identical precision/scale in embedded and
+client/server modes
+
+2005.01.16 1.8.0.RC3
+
+Regression bug fixes.
+New property allows a CHECKPOINT DEFRAG to be performed automatically whenever
+CHECKPOINT is performed internally or via a user command.
+
+SET CHECKPOINT DEFRAG n
+
+The parameter n is the megabytes of abandoned space in the .data file. When
+a CHECKPOINT is performed either as a result of the .log file reaching the
+limit set by "SET LOGSIZE m", or by the user issuing a CHECKPOINT command, the
+amount of space abandoned during the session is checked and if it is larger
+than n, a CHECKPOINT DEFRAG is performed instead of a checkpoint.
+
+2005.01.14 1.8.0.RC2
+
+Regression bug fixes.
+
+
+2005.01.10 1.8.0.RC1
+
+Allows embedding into OpenOffice.org
+Rewrite of log and cache handling classes, including:
+New deleted block manager with more effective deleted block reuse.
+Faster log processing after an abnormal termination.
+Better checks when maximum data file size is reached.
+Better recovery when maximum data file size is reached.
+
+Changes to row access to use iterators. More code clarity.
+
+Various refactorings and new package for improved modularity.
+
+Enhancements to DatabaseManagerSwing
+
+In all other respects, 1.8.0.RC1 is identical to 1.7.3.1
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_1.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_1.txt
new file mode 100644
index 0000000..41c8766
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_1.txt
@@ -0,0 +1,304 @@
+
+Version 1.7.1 improves performance and fixes several bugs that have come to light since the release of 1.7.0. It does not feature any major new functionality in the database engine.
+
+*Over ten-fold speedup of function calls in queries introduced in 1.7.1.
+
+*Up to 30% reduction in memory used by indexes and table rows, resulting in smaller overall memory footprint in 1.7.1.
+
+*Linux scripts for starting and shutting down server instances in 1.7.1.
+
+*Linux build scripts in 1.7.1.
+
+*The Transfer Tool was enhanced for this version by Nicolas Bazin and Bob Preston.
+
+HSQLDB version 1.7.0 CHANGELOG SINCE VERSION 1.60
+
+* Enhancements to SQL
+
+LIMIT and TOP keywords
+
+The LIMIT keyword was introduced in 1.61 with limited functionality. In 1.7.0 the functionality has been fully extended:
+
+SELECT LIMIT <n> <m> DISTINCT is now allowed.
+
+SELECT LIMIT <n> <m> ... is now treated as a complete SELECT statement and can be used anywhere a SELECT is used, so statements such as the following return meaningful results:
+
+SELECT LIMIT <n> <m> ... WHERE <x> IN (SELECT LIMIT <o> <p> ... )
+
+SELECT LIMIT <n> <m> ... UNION SELECT LIMIT <o> <p>
+
+TOP <m> is synonymous with LIMIT 0 <m>
+
+GROUP BY keyword
+
+GROUP BY had several problems and bugs that have now been resolved. The results are now correct regardless of the order of selected columns or when sorting by multiple columns.
+
+DEFAULT keyword
+
+This keyword has been introduced with full functionality for defining default values for table columns. Special cases 'CURRENT_DATE','CURRENT_TIME','CURRENT_TIMSTAMP', 'TODAY' and 'NOW' can set DATE, TIME and TIMESTAMP columns with current values when an INSERT statement is executed.
+
+SIZE and PRECISION
+
+Maximum column sizes for CHAR, VARCHAR, and other types are now stored in the database. The CHAR and VARCHAR sizes can be enforced when INSERT, UPDATE and SELECT ... INTO table operations are performed. The enforcement is optional and turned off by default.
+
+SAVEPOINT for TRANSACTION
+
+New feature to allow transactions to rollback to a specified point.
+
+CONSTRAINTS and INDEXES
+
+Primary keys declared as CONSTRAINT <name> PRIMARY KEY, either on a single column or on multiple columns, are now accepted and used. All constrains are named, with those generated by the system given unique names as SYS_CT_<n>.
+
+Each INDEX must have a unique name within the database. This conforms to SQL standards.
+
+FOREIGN KEYS, ON DELETE CASCADE
+
+Foreign key constraints referencing the same table are now allowed. New, stricter rules require a unique index to exist on the referenced column (this is the recommended behaviour for new databases but is turned off by default for existing databases).
+
+ON DELETE CASCADE qualifiers are now supported for foreign keys in data definition scripts. These qualifiers are enforced with fast searches on underlying indexes.
+
+New support for ALTER TABLE allows 'forward-referencing' foreign keys where the referencing table is created before the referenced table.
+
+TRIGGERS
+
+New multiple-row trigger queues are introduced to improve performance. Enhancements to prevent deadlocks are also added.
+
+TEMP tables
+
+Full support for session-specific temporary tables is introduced. TEMP tables can be used in any statement the same way as ordinary tables, the differences are they are not visible to other session and are dropped when the session is closed. Also, FOREIGN KEY constraints for ordinary tables cannot reference a TEMP table for obvious reasons (TEMP tables can have foreign keys that reference any ordinary or temp table).
+
+TEXT tables
+
+Full support for delimited text files (such as CSV) as the data source for SQL tables.
+
+VIEWS
+
+Views are supported as global objects. Internally, each time the view is used, the underlying select statement is performed. Views can be created and dropped using the following statements.
+
+
+CREATE VIEW <viewname> AS SELECT ... FROM ... WHERE ....
+DROP VIEW <viewname> {IF EXISTS}
+
+ALTER
+
+The following statements are now supported:
+
+ALTER TABLE <name> RENAME TO <newname>
+
+All tables can now be renamed.
+
+ALTER TABLE <name> ADD COLUMN <column definition> [BEFORE <existing name>]
+ALTER TABLE <name> DROP COLUMN <colname>
+
+A column can be added to the column list, so long as its definition does not include PRIMARY KEY or IDENTITY keywords. If a DEFAULT clause is used in the definition, its value is used in all the existing rows. Any column can be dropped unless it is part of the column list for a constraint or index.
+
+ALTER TABLE <name> DROP CONSTRAINT <constname>
+
+Any constraint apart from primary key can be dropped. The index backing the constraint is dropped if not referenced by a foreign key.
+
+ALTER TABLE <name> ADD CONSTRAINT <constname> UNIQUE <column list>
+
+Unique constraints can be added. A new index is created if necessary.
+
+ALTER TABLE <name> ADD CONSTRAINT <constname> FOREIGN KEY <foreign key definition>
+
+Both backward and forward referencing foreign keys are supported.
+
+ALTER INDEX <name> RENAME TO <newname>
+
+Any index can be renamed, so long as it is not a primary key index or an automatically created index on the referencing columns of a foreign key.
+
+DROP INDEX <name>
+
+Any index can be dropped, so long as it is not a primary key index or an automatically created index on the referencing columns of a foreign key or an index backing a constraint.
+
+SQL NAMES
+
+Full support for quoted SQL object names which can include any Unicode character. This applies to TABLE, COLUMN, CONSTRAINT and INDEX names.
+
+* Functions
+
+SET FUNCTION such as COUNT AVG SUM now accept the DISTICT parameter. This feature is
+supported only when GROUP BY is not used in the query.
+
+A number of bugs in functions such as ABS, CONCAT and SUBSTR have been fixed.
+
+A small number of new functions have been added.
+
+The SOUNDEX function has been rewritten according to standards.
+
+* Expressions
+
+Arithmetic expressions in SQL statements are now fully supported. Previously, when an arithmetic expression was used to INSERT or UPDATE a value, the first term had to be of the same type as the columns. For example 2*1.2 could not be inserted into a DECIMAL or DOUBLE column. Now all expressions are evaluated and the resulting value can be inserted into a column so long as it can be converted without narrowing.
+
+More lenient treatment of values for TIMESTAMP columns in INSERT and UPDATE now allows a DATE or part TIMESTAMP string to be used instead of the full pattern.
+
+BIT columns can be initialised with numeric values in addition to true and false. Numeric value 0 represents false; all other values represent true.
+
+* Locales
+
+CHAR, VARCHAR and LONGVARCHAR columns can now be sorted according to the current JVM locale. This feature is optional and turned off by default. If turned on, it can slow down database operations, especially where indexes on CHAR columns and its variant are used.
+
+* Error Trapping
+
+Some errors in SQL statements that were not reported before and resulted in potentially incorrect data are now caught.
+
+Dropping tables that are referenced by foreign key constraints from other tables is now disallowed regardless of the system-wide REFERENTIAL_INTEGRITY setting.
+
+Duplicate column names in one table are no longer allowed.
+
+Duplicate index names are no longer allowed.
+
+Using system table names for user tables is disallowed.
+
+INSERT INTO table (a,b,c,...) VALUES (x,y,z,...) statements require the count of names and values to match.
+
+* Enhancements to JDBC
+
+JDBC ResultSet objects are now scrollable and fully support absolute and relative positioning.
+
+Extra getXXX() methods are now supported, including getAsciiStream(), getUnicodeStream(), getCharacterStream().
+
+Optional use of column labels (aliases) as the return value for getColumnName(int i) calls. This is turned off by default.
+
+JDBC PreparedStatement support has been enhanced with support for setting and reading Date, Time and Timestamp values with a given Calendar object. This allows, among others, specifying different time zones for values that are set or read.
+
+Extra setXXX() methods are now supported, including setAsciiStream(), setUnicodeStream(), setCharacterStream().
+
+setObject() methods of PreparedStatement have been improved to allow storage of any serializable object in columns of SQL type, OTHER.
+
+JDBC DatabaseMetaData getImportedKeys(), getExportedKeys(), getCrossReference(), getBestRowIdentifier() are now supported.
+
+* Interoperability Enhancements
+
+HsqlServerFactory allows interoperability with application servers.
+
+An embedded server (an HSQLDB server started inside another application) can be directed to avoid calling System.exit() when the SHUTDOWN command is issued to the database for admin purposes.
+
+javax.jdbc.DataSource interface has been introduced as an experimental feature. In order to include this support, the source code should be compiled with JDK 1.4 or with appropriate J2EE jars present in the class path.
+
+* Performance Enhancements
+
+Very large CHAR, VARCHAR, LONGVARCHAR values are now supported in all types of tables.
+
+Major overhaul of internal operations to drastically reduce creation of temporary objects and type conversion.
+
+Code enhancements to reduce unnecessary method calls in loops.
+
+Enhancements to avoid duplicate indexes (in source code but not activated).
+
+Over ten-fold speedup of function calls in queries intoduced in 1.7.1.
+
+Up to 30% reduction in memory used by indexes and table rows, resulting in smaller overall memory footprint in 1.7.1.
+
+* Reliability Enhancements
+
+Many bugs that existed in 1.43 have been fixed.
+
+Better catching of error conditions and special cases such as null values.
+
+Correct treatment of large binary data.
+
+Better enforcement of internal data consistency in a number of areas.
+
+* Utilities
+
+New Script Tool class allows executing an SQL script.
+
+Enhancements to Transfer Tool to allow the user to save the transfer settings and load them in future sessions. Additional enhancements to support different database source and targets in a modular way.
+
+Swing version of Database Manager.
+
+Linux scripts for starting and shutting down server instances in 1.7.1.
+
+* Build
+
+Better Ant build with automatic detection of JDK version
+
+Linux build scripts in 1.7.1
+
+List of patches and fixes numbered by SourceForge Tracker ID's.
+
+416437 by deforest@users - JDBC DataSource
+418017 by deforest@users - made optional
+437174 by hjb@users - cache enhancements
+442993 by fredt - mixed type arithmetic expressions
+448121 by sma@users - large binary values - part implemented
+489917 by jytou@users - optional getColumnName(int) return value
+450412 by elise@users - jdk 1.1 compatibility
+450455 by kibu@users - platform specific line endings in .scrip file
+455757 by galena@users (Michiel de Roo)
+455785 by hjbusch@users - large DECIMAL inserts
+456679 by hiep256@users - TOP keyword
+460907 by fredt - soundex
+461556 by paul-h@users - compatibility with application servers
+471710 by fredt - LIMIT rewritten
+473613 by thertz@users - error trapping for joins
+475199 by fredt - duplicate column
+475586 by wreissen@users - servlet database name
+476650 by johnhobs@users - GROUP BY aggregates
+476694 by velichko@users - transaction savepoints
+478657 by peterhudson@users - improved TRIGGER support
+481239 by xponsard@users - enhancement to Transfer Tool
+481239 by yfl@users - SQL script execution
+485704 by boucherb@users - null binary objects
+488200 by xclay@users - throw exception
+489184 by xclay@users - thread safety
+489777 by fredt - protection of system tables
+491987 by jimbag@users - column size enforcement and preservation
+495484 by boucherb@users - exception at shutdown
+495938 by johnhobs@users - GROUP BY sorting
+497714 by lakuhns@users - scrollable JDBC result sets
+497872 by Nitin Chauhan - performance enhancements
+497872 by Nitin Chauhan - default labels for aggregates
+500767 by adjbirch@users - TransferTool enhancements
+505356 by daniel_fiser@users - sorting according to Locale
+509002 by fredt - correct parsing of primary key constraints
+513005 by sqlbob@users - ABS function
+513005 by sqlbob@users - HOUR function
+513005 by sqlbob@users - TEMP tables
+513005 by sqlbob@users - TEXT TABLE support
+514111 by fredt - CONCAT function
+517028 by peterhudson@users - JDBC setDate(), etc. with Calendar
+521078 by boucherb@users - DROP TABLE checks
+523880 by leptitpre@users - VIEW SUPPORT
+544754 by sqlbob@users - RAWTOHEX and HEXTORAW functions
+549741 by velichko@users - RENAME for tables and indexes
+550970 by boucherb@users - fewer StringBuffers
+552830 by rougier@users - COUNT(DISTICT column)
+580430 by thomasm@users - wrong column name in getIndexInfo()
+
+List of enhancements without patch number
+
+1.7.0 by boucherb@users - maintaining constraint names
+1.7.0 by boucherb@users - self referenced foreign keys
+1.7.0 by boucherb@users - stubs for JDBC3 methods and updated Javadoc
+1.7.0 by boucherb@users - Javadoc for a number of classes
+1.7.0 by deforest@users - create database directory if not exists
+1.7.0 by fredt - full support for quoted identifiers
+1.7.0 by fredt - ON DELETE CASCADE qualifier for foreign keys
+1.7.0 by fredt - foreign keys without target column list
+1.7.0 by fredt - DEFAULT keyword in column definitions
+1.7.0 by fredt - GROUP BY with multiple columns in groups
+1.7.0 by fredt - JDBC getDate, etc. with Calendar
+1.7.0 by fredt - lenient handling of Timestamp inserts
+1.7.0 by fredt - JDK 1.1 compatible deque object backed by an array
+1.7.0 by fredt - new HsqlProperties class
+1.7.0 by fredt - preservation of column size, etc. with SELECT INTO
+1.7.0 by fredt - ensuring internal consistency of Result objects
+1.7.0 by fredt - resolving some deprecation warnings
+1.7.0 by fredt - ALTER TABLE for adding and dropping columns and constraints
+1.7.0 by fredt - revamped storage of cached table with very large strings
+1.7.0 by fredt - management of server connections with optional no system exit
+1.7.0 by fredt - revamped management of server and database properties
+1.7.0 by fredt - JDBC getUnicodeStream(), getAsciiStream(), getCharacterStream()
+1.7.0 by fredt - JDBC setAsciiStream(), setUnicodeStream(), setCharacterStream()
+1.7.0 by fredt - JDBC getCrossReference(), getImportedKeys(), getExportedKeys()
+1.7.0 by nbazin@users - enhancements to Transfer Tool
+1.7.0 by sqlbob@users - reengineering of Database Manager and Transfer Tool
+1.7.0 by sqlbob@users - TEMP, TEXT and CACHED table targets for SELECT INTO
+1.7.0 by sqlbob@users - improvements to cache size management
+1.7.0 by David Moles - tests for subselect
+1.7.0 by jrmaher@users - improvements to Script Tool
+
+also a large number of error-trapping and other fixes not documented
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_2.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_2.txt
new file mode 100644
index 0000000..f99d65e
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_7_2.txt
@@ -0,0 +1,532 @@
+HSQLDB 1.7.2 CHANGE LOG
+
+
+The development of 1.7.2 began in late 2002 with a plan to release the new version within 6 months. Several alpha versions, culminating in ALPHA_M, were released in the first three months and featured most of the intended enhancements. However, when newly written code for system tables was introduced, many changes had to be made to internal code to accommodate the reporting requirements. This was followed from around April 2003 with efforts to separate query compilation from execution. Other developments to allow multiple databases, better query processing, more advanced SQL keywords, etc. took place simultaneously, resulting in an extended scope for 1.7.2 and extensive addition and rewrite of several key classes. The next alpha version was released in September, followed by a further six, until the first Release Candidate became available at the end of 2003. Since then, all efforts have been focused on fixing bugs and inconsistencies, with 7 additional Release Candidates issued.
+
+As a result, 1.7.2 features major changes to the database engine. Existing applications that work with previous versions may need modifications to work with the new version. Changes are listed here and in the rest of the documentation.
+
+I would like to thank all developers, testers and users who have contributed to this effort.
+
+
+June 2004
+
+Fred Toussi
+
+Maintainer, HSQLDB Project
+http://hsqldb.sourceforge.net
+
+
+----------------------------------------------------
+----------------------------------------------------
+
+SQL ENHANCEMENTS AND CHANGES
+
+
+----------------
+
+DDL
+
+Some new restrictions have been imposed:
+
+CONSTRAINT names must be unique within each database (same with INDEX names).
+Size / precision / scale values for several types are now disallowed. Allowed types are: CHAR(n), VARCHAR(n), DOUBLE(n), DECIMAL(n,m)
+
+In column default value specification, functions such as CURRENT_TIME, CURRENT_DATA, etc. should not be enclosed in quotes. New function CURRENT_USER can also be used.
+
+SQL keywords are not allowed as table or column names unless they are double-quoted.
+
+----------------
+
+VIEW
+
+
+View definitions can now have a column name list:
+
+CREATE VIEW <viewname> [(<colnmae>, ...)] AS SELECT ....
+
+ALTER TABLE commands take into account the views that reference the table and prevent illegal changes.
+
+
+
+----------------
+
+CHECK
+
+
+
+Support for CHECK constraints that apply to the modified/inserted row only. This can be added via ALTER TABLE ADD CHECK() or in table definition.
+
+
+
+----------------
+
+QUERY PROCESSING
+
+
+
+Query processing has been extensively enhanced in this release and better SQL standard compliance has been achieved. Major implications of the recent changes are as follows:
+
+Columns in correlated subqueries are resolved independently first. If there is an unresolved column, then the surrounding context is used to resolve it. This is opposite the resolution order previously enforced in the engine.
+
+Some ambiguities and errors in ORDER BY clauses are now caught.
+
+UNION and other set queries accept only one ORDER BY clause at the end. In this clause, column indexes or column names in the first select are allowed as sort specification e.g.:
+
+SELECT .. UNION SELECT .. ORDER BY 1 DESC, 5, 3
+
+The implemntation of UNION, EXCEPT and INTERSECT set operations has been rewritten to comply with SQL standards.
+
+When multiple set operations are present in a query, they are now evaluated from left to right, with INTERSECT taking precedence over the rest.
+
+It is now possible to use parentheses around multiple (or single) select statements with set operations to change the order of evalation.E.g.:
+
+((SELECT * FROM A EXCEPT SELECT * FROM B) INTERSECT SELECT * FROM D UNION SELECT * FROM E)
+
+The above applies to all cases where a SELECT can be used except a single value select inside another select. Eg.
+
+SELECT a, b, SELECT asinglevalue FROM anothertable WHERE ..., FROM atable JOIN ...
+
+----------------
+
+IMPROVEMENTS TO UPDATE AND INSERT
+
+
+
+Certain types of UPDATES and INSERTS that previously failed due to blanket application of UNIQUE constraints now work.
+
+Examples include UPDATE ... SET col = col + 1 where col is an identity column or INSERT a self referencing row under FOREIGN key constraints.
+
+
+
+----------------
+
+AGGREGATES, GROUP BY, HAVING
+
+
+
+DISTINCT aggregates are now supported.
+
+Aggregates on all numeric type columns are now supported. Expressions are allowed as aggregate function parameter.
+
+SUM returns a BIGINT for TINYINT, SMALLINT and INTEGER columns. It returns a DECIMAL for BIGINT columns (scale 0). SUM of a DECIMAL column has the same scale as the column.
+
+AVG returns the same type as the column or the expression in its argument.
+
+Aggregates with GROUP BY do not return any rows if table is empty
+
+Fully enforced GROUP BY rules including support for HAVING conditions
+
+
+----------------
+
+JOINS
+
+
+
+Extensive rewrite of join processing abolishes the requirement for an index on any joined columns.
+
+Problems with OUTER and INNER joins returning incorrect results have been fixed and results are correct in all cases.
+
+When two tables are joined, rows resulting from joining null values in the joined columns are no longer returned.
+
+Most expressions are supported in the join condition (JOIN <table> ON ....).
+
+Outer join conditions can now include most comparison operators, as well as OR logical operators. For example:
+
+LEFT OUTER JOIN atable ON a=b AND c>d OR a=2 ...
+
+Illegal forward table references are no longer allowed in join conditions.
+
+There are many other small improvements and fixes, including:
+
+
+
+----------------
+
+NULLS
+
+
+
+Support for multiple rows with null fields under unique constraints.
+
+Exclusion of NULL values from results of queries with range conditions.
+
+
+
+----------------
+
+FOREIGN KEY
+
+
+
+Full support for triggered actions, including foreign keys that reference the same table.
+
+FORIEGN KEY ... ON UPDATE { CASCADE | SET NULL | SET DEFAULT } ON DELETE { CASCADE | SET NULL | SET DEFAULT }
+
+Strict treatment of foreign key constraint requirements is now enforced. A foreign key declaration _requires_ a unique constraint to exist on the columns of the referenced table. This applies both to old and new databases. Duplicate foreign keys (with exactly the same column sets) are now disallowed.
+
+
+
+----------------
+
+SEQUENCE
+
+
+
+Support for sequences. Identity columns are now automatic sequence primary key columns that can be defined as INTEGER or BIGINT as follows:
+
+GENERATED BY DEFAULT AS IDENTITY (START WITH <n>, INCREMENT BY <m>)
+
+Named sequence objects can be defined with:
+
+CREATE SEQUENCE <sequencename> [AS {INTEGER | BIGINT}] [START WITH <startvalue>] [INCREMENT BY <incrementvalue>];
+
+And the next value can be retrieved with the following expression in SELECT, INSERT and UPDATE queries:
+
+NEXT VALUE FOR <sequencename>
+
+
+
+----------------
+
+SQL FUNCTIONS
+
+
+Added support for a range of SQL style functions:
+
+
+CASE .. WHEN .. THEN .. [WHEN .. THEN ..] ELSE .. END
+
+CASE WHEN .. THEN .. [WHEN .. THEN ..] ELSE ... END
+
+NULLIF(.. , ..)
+
+SUBSTRING(.. FROM .. FOR ..)
+
+POSITION(.. IN ..)
+
+TRIM( {LEADING | TRAILING .. } FROM ..)
+
+EXTRACT({DAY | TIME |..} FROM ..)
+
+COALESCE(.. , ..)
+
+
+
+----------------
+
+TRIGGER
+
+
+
+It is now possible to execute triggers in the main execution thread. This allows uses for triggers that were not possible before, especially checking and modifying inserted values.
+
+
+
+----------------
+
+DATETIME
+
+
+
+Fixed the TIMESTAMPS, TIME and DATE normalisation issues.
+
+
+
+----------------
+
+OTHER
+
+
+
+IN value lists can now contain column values or expressions. See TestSelfQueries.txt for an example.
+
+
+LIKE has been debugged and optimised when possible.
+
+
+
+----------------------------------------------------
+----------------------------------------------------
+
+JDBC ENHANCEMENTS
+
+
+
+JDBC support for savepoints.
+
+Support for JDBC batch execution with multiple-results. Both Statement and PreparedStatement batch modes are supported.
+
+SSL support for server mode operation.
+
+After calling Statement.setMaxRows(int), the maximum row count restriction will no longer apply to result sets returned and used internally. (change in 1_7_2_5)
+
+
+----------------
+
+CONNECTION PROPERTY
+
+
+
+A new property, ifexists={true|false} can be specified for connections. It has an effect only on connections to in-process databases. The default is false and corresponds to current behaviour.
+
+If set true, the connection is opened only if the database files have already been created -- otherwise no new database is created and the connection attempt will fail. Example:
+
+jdbc:hsqldb:hsql:file:mydb;ifexists=true
+
+This property is intended to reduce problems resulting from wrong URL's which get translated to unintended new database files. It is recommended to use this property for troubleshooting.
+
+Database properties can be specified for the first connection to a new file: or mem: database. This allows properties such as enforce_strict_size to be specified for mem: databases, or for a new file: database.
+
+jdbc:hsqldb:hsql:mem:test;sql.enforce_strict_size=true
+
+
+
+----------------
+
+PREPARED STATEMENTS
+
+
+
+Support for real PreparedStatements - major speedup. This has introduced the following changes from the previous versions.
+
+The execute(String sql), executeUpdate(String sql) and executeQuery(String sql) commands are no-longer supported for PreparedStatements according to JDBC specs. Use an ordinary Statement for calling these methods.
+
+The SQL for each call to the prepareStatement() method of Connection must consist of a single SQL query. For multiple statements use either multiple PreparedStatement objects or an ordinary Statement object.
+
+Bug fixes ensure date / time, java object and binary values stored in in-process databases via prepared statements will not be altered if the object is modified outside the engine.
+
+Full support for ResultSetMetaData
+
+Full support for ParameterMetaData
+
+Support for CLOB methods in ResultSet
+
+
+
+----------------
+
+TRANSACTIONS VIA WEB SERVER
+
+
+
+Uniform support for transactions via HSQL and HTTP (WebServer and Servlet) protocols
+
+
+----------------------------------------------------
+----------------------------------------------------
+
+OTHER ENHANCEMENTS
+
+
+
+----------------------------------------------------
+
+SPEED
+
+
+
+Speed optimisation of joins with views and subqueries, using indexes to optimise join performance.
+
+Improved index use for multiple key joins.
+
+Further speed improvements in all logged modes
+
+INSERT and UPDATE ops are faster by 5-20% in MEMORY tables, less in CACHED tables.
+
+General speedup of CACHED table operation due to better management of the memory cache.
+
+
+
+----------------------------------------------------
+
+DATABASE PACKAGING AND MODES
+
+
+
+Two new options for databases: files_readonly and files_in_jar were added:
+
+
+FILE READ-ONLY
+
+
+If the property hsqldb.files_readonly=true is set in the database .properties file, no attempt is made to write the changes to data to file. Default, MEMORY tables can be read/write but TEXT and CACHED tables are treated as read-only.
+
+
+FILES IN JAR
+
+
+This option allows database files to be distributed in the application jar. We have changed the original contribution so that a special URL is used for this mode in the form of:
+
+jdbc:hsqldb:res:<path in jar>
+
+The URL type 'res' determines that the path that follows is a path into the JAR. The path must be all lowercase and begin with a forward slash.
+
+The database can be readonly or files_readonly, depending on the value set in .properties file.
+
+
+'OTHER' DATA TYPE
+
+
+Change to handling of OTHER columns. It is no longer required that the classes for objects stored in OTHER columns to be available on the path of an HSQLDB engine running as a server. Classes must be available on the JDBC client's path.
+
+
+----------------------------------------------------
+
+MULTIPLE IN-MEMORY AND SERVER DATABASES
+
+
+
+Support for multiple memory-only databases within the same JVM
+
+Support for simultaneous multiple servers on different ports, multiple internal connections and multiple databases within the same JVM
+
+Each HSQLDB server or webserver can now serve up to 10 different databases.
+
+The server.properties and webserver.properties method for defining the databases has changed. The following properties should be used:
+
+server.database.0 path_of_the_first_database
+server.dbname.0 alias_for_the_first_database
+
+Up to 10 databases can be defined but they must start from 0. The same applies to command line arguments for Server and WebServer.
+
+The URL's for connecting to servers should have the alias of the database at the end. For example, to connect to the HSQL protocol server on the localhost use:
+
+jdbc:hsqldb:hsql://localhost/alias_for_the_database
+
+where alias_for_the_database is the same string as defined in server.properties as server.dbname.n
+
+If not explicitly set, the default for server.dbname.0 is "" (empty string) so that old URL types continue to work.
+
+Multiple memory-only database are supported by the use of:
+
+jdbc:hsqldb:mem:alias_for_the_first_database
+jdbc:hsqldb:mem:alias_for_the_second_database
+
+Examples: jdbc:hsqldb:mem:db1 jdbc:hsqldb:mem:mydb
+
+The connection type, 'file:', can be used for file database connections. Example below:
+
+jdbc:hsqldb:file:mydb;ifexists=true
+
+The URL for connecting to a Servlet HTTP server must have a forward-slash at the end. Servlet serves only one database.
+
+jdbc:hsqldb:hsql://localhost:8080/servlet/HsqlServlet/
+
+
+----------------------------------------------------
+
+DATABASE METADATA
+
+
+System table support and java.sql.DatabaseMetadate have been overhauled.
+
+Use SELECT * FROM SYSTEM_TABLES to see the full list.
+
+
+
+----------------------------------------------------
+
+TEXT TABLES
+
+
+Enhanced TEXT table handling and reporting of errors in CSV (source) files
+
+TEXT TABLES encoding of the source file can now be specified. UTF-8 and other encodings can be used.
+
+
+
+----------------------------------------------------
+
+MEMORY USE AND OBJECT POOLING
+
+
+An Object pool has been incorporated. This reduces memory usage to varying degrees depending on the contents of database tables and speeds up the database in most cases. Currently the size of the pool is hard-coded but it will be user adjustable in a future version.
+
+
+
+----------------------------------------------------
+
+PERSISTENCE
+
+
+----------------
+
+CHECKPOINT DEFRAG
+
+Defragments the *.data file without shutting down the database
+
+
+----------------
+
+SET SCRIPTFORMAT {TEXT | BINARY | COMPRESSED }
+
+Changes the format of the *.script file and performs a checkpoint.
+
+Database script can be stored in binary or compressed binary formats, resulting in smaller size and faster loading.
+
+
+----------------
+
+The *.script file now contains only the DDL and data that is written at CHECKPOINT or SHUTDOWN. The COMPRESSED format has the side benefit of hiding the DDL and the admin password.
+
+The *.log file now contains the statements executed since the last startup or CHECKPOINT. This file is in plain text format.
+
+----------------
+
+SET WRITE_DELAY {TRUE | FALSE}
+
+SET WRITE_DELAY <n>
+
+The behaviour of SET WRITE_DELAY has changed with the introduction of the sync() method to force the log to be written out completely to disk at given intervals.
+
+SET WRITE_DELAY {TRUE | FALSE} is interpreted as synch every 60 seconds or 1 second. SET WRITE_DELAY <n> where n is an integer is interpreted as synch every n seconds. The current default is 60 seconds which seems to provide the right balance. Under heavy INSERT/DELETE/UPDATE test conditions, the performance impact of SET WRITE_DELAY 1 is probably about 15% over that of SET WRITE_DELAY 300.
+
+Crash recovery has been modified so that any line in the *.log file that is not properly written (and causes an error) ends the redo process. A message is reported to the user, instead of stopping engine operation.
+
+----------------
+
+NIO ACCESS FOR *.data FILES
+
+New nio access layer for .data files speeds up most CACHED TABLE related operations very significantly. 90% speedups in TestCacheSize tests have been observed.
+
+There must be enough available memory in the machine to allow a memory-mapped buffer for the entire *.data file. Beyond this size, the engine reverts to non-nio access.
+
+
+
+----------------------------------------------------
+
+BUILD
+
+Reduction in JDK / JRE dependencies (see readmebuild.txt)
+
+The supplied JAR is now compiled with JDK 1.4 and requires a JRE 1.4 or later to work. You can rebuild the JAR with JDK 1.3.x in order to use it with JRE 1.3 or earlier.
+
+
+
+----------------------------------------------------
+
+DOCUMENTATION
+
+
+Documentation is now maintained mainly in XML format with HTML and PDF versions available.
+
+
+
+----------------------------------------------------
+
+UTILITIES
+
+
+The SQL Tool is a powerful new utility in 1.7.2 and allows processing SQL commands via the shell or scripts.
+
+The Transfer Tool utility saw a major upgrade just before the 1.7.2 release cycle. In this release some minor updates and bug fixes, together with significant speedup, have been intoduced.
+
+The Database Manager has been enhanced slightly to include a command to save the result set in CSV format. The Swing version of Database Manager allows the user to sort the rows of the result set on any column.
+
+The connection dialogue in the AWT version of Database Manager and Transfer Tool allows saving and recalling connection URL's together with the user name and password.
+
+
+----------------------------------------------------
+
+END
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_8_0.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_8_0.txt
new file mode 100644
index 0000000..0a50153
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/changelog_1_8_0.txt
@@ -0,0 +1,287 @@
+
+HSQLDB 1.8.0 CHANGE LOG
+
+
+The development of 1.8.0 began in mid 2004 with a plan to release the new version in 2005. The main feature planned for this release was the ability to be used with OpenOffice.org 2.0 as the default database engine. Release candidate versions started to appear in January, culminating in RC10 in May. Several new and enhanced SQL commands have been introduced and new capabilities such as support for multiple SCHEMA objects in each database, database-wide collations and SQL ROLE objects have been added. Parts of the persistence engine have been rewritten for better performance and long-running online operation.
+
+
+I would like to thank all developers, testers and users who have contributed to this effort.
+
+
+June 2005
+
+Fred Toussi
+
+Maintainer, HSQLDB Project
+http://hsqldb.sourceforge.net
+
+
+SQL ENHANCEMENTS
+
+----------------
+
+SCHEMAS
+
+Support for SQL schemas. Each database can contain multiple schemas. The following commands have been introduced:
+
+CREATE SCHMEA <schema name> AUTHORIZATION DBA
+DROP SCHEMA <schema name> {CASCADE | RESTRICT}
+ALTER SCHEMA <schema name> RENAME TO <new name>
+SET SCHEMA <schema name>
+
+Initially, the default user schema will be created with the name PUBLIC. This schema can be renamed or dropped. When the last user schema has been dropped, an empty default schema with the name PUBLIC is created.
+
+System tables all belong to INFORMATION_SCHEMA. To access system tables, either SET SCHEMA INFORMATION_SCHEMA should be used once or they should be referred to by fully specified names, e.g. INFORMATION_SCHEMA.SYSTEM_TABLES
+
+Similarly all database objects apart from columns can be referenced with fully qualified schema names.
+
+The CREATE SCHEMA command can be followed by other CREATE and GRANT commands without an intervening semicolon. All such commands are executed in the context of the newly created schema. A semicolon terminates an extended CREATE SCHEMA command.
+
+----------------
+
+ROLES
+
+Support for SQL standard roles.
+
+CREATE ROLE <role name>
+GRANT ... TO <role name>
+REVOKE ... FROM <role name>
+GRANT <role name> TO <user name>
+DROP ROLE <role name>
+
+The GRANT and REVOKE commands are similar to those used for granting permissions on different objects to USER objects. A role can then be granted to or revoked from different users, simplifying permission management.
+
+----------------
+
+GLOBAL TEMPORARY TABLES
+
+The implementation of temporary tables has changed to conform to SQL standards.
+
+The definition of a GLOBAL TEMPORARY table persists with the database. When a session (JDBC Connection) is started, an empty instance of the table is created. Temporary tables can be created with (the default) ON COMMIT DELETE ROWS or ON COMMIT PRESERVE ROWS added to table definition. With ON COMMIT PRESERVE ROWS, the table contents are not cleared when the session commits. In both cases, the contents are cleared when the session is closed.
+
+----------------
+
+SCHEMA MANIPULATION COMMANDS
+
+Several schema manipulation commands have been enhanced.
+
+Tables, views and sequences can be dropped with the CASCADE option. This silently drops all tables and views that reference the given database object.
+
+DROP TABLE <table name> [IF EXISTS] [CASCADE];
+DROP VIEW <view name> [IF EXISTS] [CASCADE];
+DROP SEQUENCE <sequence name> [IF EXISTS] [CASCADE];
+
+ALTER TABLE <table name> DROP [COLUMN] now silently drops any primary key or unique constraint declared on the column (excluding multi-column constraints).
+
+ALTER TABLE <table name> ADD [COLUMN] now accepts primary key and identity attributes.
+
+----------------
+
+COLUMN MANIPULATION
+
+Support for converting type, nullability and identity attributes of a column
+
+ALTER TABLE <table name> ALTER [COLUMN] <column name> <column definition>
+
+<column definition> has the same syntax as normal column definition. The new column definition replaces the old one, so it is possible to add/remove a DEFAULT expression, a NOT NULL constraint, or an IDENTITY definition. No change to the primary key is allowed with this command.
+
+- The column must already be a PK column to accept an IDENTITY definition.
+- If the column is already an IDENTITY column and there is no IDENTITY definition, the existing IDENTITY attribute is removed.
+- The default expression will be that of the new definition, meaning an existing default can be dropped by omission, or a new default added.
+- The NOT NULL attribute will be that of the new definition, similar to above.
+- Depending on the conversion type, the table may have to be empty for the command to work. It always works when the conversion is possible in general and the individual existing values can all be converted.
+
+A different syntax can be used to change the next value from an IDENTITY column:
+
+ALTER TABLE <table name> ALTER [COLUMN] <column name> RESTART WITH <n>
+
+----------------
+
+ADDING AND DROPPING PRIMARY KEYS
+
+It is now possible to add or drop a primary key.
+
+An existing primary key that is to be removed should not be referenced in a FOREIGN KEY constraint. If a table has an IDENTITY column, removing a primary key will remove the identity attribute of the column but leave the actual data.
+
+When adding a primary key, a NOT NULL constraint is automatically added to the column definitions. The table data for the columns of a newly declared primary key should not contain null values.
+
+ALTER TABLE <name> ADD CONSTRAINT <cname> PRIMARY KEY(collist);
+ALTER TABLE <name> DROP CONSTRAINT <cname>;
+ALTER TABLE <name> DROP PRIMARY KEY; // alternative syntax
+
+----------------
+
+SIZE ENFORCEMENT
+
+
+The database property sql.enforce_strict_size=true has now a wider effect.
+
+Previously CHAR /VARCHAR lengths could be checked and padding performed only when inserting / updating rows. Added support for CHAR(n), VARCHAR(n), NUMERIC(p,s) and DECIMAL(p,s) including SQL standard cast and convert semantics. CHAR and VARCHAR declarations now require a size parameter. A CHAR declaration without a size parameter is interpreted as CHAR(1). TIMESTAMP(0) and TIMESTAMP(6) are also supported, with the precision representing the sub-second resolution.
+
+Explicit CAST(c AS VARCHAR(2)) will always truncate the string. Explicit CAST(n AS NUMERIC(p)) will always perform the conversion or throw if n is out of bounds. All other implicit and explicit conversions to CHAR(n) and VARCHAR(n) are subject to SQL standard rules.
+
+----------------
+
+ALL and ANY expressions
+
+Full support for ALL(SELECT ....) and ANY(SELECT ....) with comparison operators: =, >, <, <>, >=, <=
+Example:
+
+SELECT ... WHERE <value expression> >= ALL(SELECT ...)
+
+LIMIT and OFFSET
+
+New alternative syntax for LIMIT at the end of the query:
+
+LIMIT L [OFFSET O]
+
+It is now possible to use LIMIT combined with ORDER BY in subqueries and SELECT statements in brackets that are terms of UNION or other set operations.
+
+An ORDER BY or LIMIT clause applies to the complete result of the UNION and other set operations or alternatively to one of its components depending on how parentheses are used. In the first example the scope is the second SELECT, while in the second query, the scope is the result of the UNION.
+
+SELECT ... FROM ... UNION
+(SELECT ... FROM ... ORDER BY .. LIMIT)
+
+SELECT ... FROM ... UNION
+SELECT ... FROM ... ORDER BY .. LIMIT
+
+
+Support for ORDER BY, LIMIT and OFFSET in CREATE VIEW statements
+
+----------------
+
+COLLATIONS
+
+Each database can have its own collation. The SQL command below sets the collation from the set of collations in the source for org.hsqldb.Collation:
+
+SET DATABASE COLLATION <double quoted collation name>
+
+The command has an effect only on an empty database. Once it has been issued, the database can be opened in any JVM locale and will retain its collation.
+
+The property sql.compare_in_locale=true is no longer supported. If the line exists in a .properties file, it will switch the database to the collation for the current default.
+
+----------------
+
+NAME RESOLUTION IN QUERIES
+
+Parsing enhancements allow all reserved SQL words to be used as identifiers when double-quoted and then used in queries. E.g. CREATE TABLE "TABLE" ("INTEGER" INTEGER)
+
+Enhancements to resolve column and table aliases used in query conditions.
+
+----------------
+
+ENHANCEMENTS
+
+Since 1.7.3, the evaluation of BOOLEAN expressions has changed to conform to SQL standards. Any such expression can be TRUE, FALSE, or UNDEFINED. The UNDEFINED result is equivalent to NULL.
+
+Optional changed behaviour of transactions in the default READ UNCOMMITTED mode. When a database property, sql.tx_no_multi_write=true has been set, a transaction is no longer allowed to delete or update a row that has already been updated or added by another uncommitted transaction.
+
+Support for correct casting of TIME into TIMESTAMP, using CURRENT_DATE
+
+
+----------------
+
+BUG FIXES
+
+Fixed reported bug with NOT LIKE and null values
+
+Fixed bug with OR conditions in OUTER JOIN
+
+Fixed bug with duplicated closing of prepared statements
+
+Fixed various parsing anomalies where SQL commands were accepted when quoted, double-quoted or prefixed with an identifier, or identifiers were accepted in single quotes. Example of a command that is no-longer tolerated:
+
+Malformed query: MY. "SELECT" ID FROM 'CUSTOMER' IF.WHERE ID=0;
+Actual query: SELECT ID FROM CUSTOMER WHERE ID=0;
+
+Fixed issue with illegal user names
+
+Fixed TEXT table implementation to maintain the commit status of rows during recovery from an abrupt shutdown. Uncommitted changes will not appear in TEXT tables.
+
+----------------
+
+STORAGE AND PERSISTENCE IMPROVEMENTS
+
+New connection property for setting the default table type when CREATE TABLE is used. The connection property, hsqldb.default_table_type=cached will set the default to CACHED tables, or the SET PROPERTY command can be used. Values, "cached" and "memory" are allowed.
+
+
+Improved support for text tables. Newline support in quoted fields is now complete. It is now possible to save and restore the first line header of a CSV file when ignore_first=true is specified. When a text table is created with a new source (CSV) file, and ignore_first=true has been specified the following command can be used to set a user defined string as the first line:
+SET TABLE <table name> SOURCE HEADER <double quoted string>.
+
+A new application log has been introduced as an optional feature. The property/value pair "hsqldb.applog=1" can be used in the first connection string to log some important messages. The default is "hsqldb.applog=0", meaning no logging. A file with the ending ".app.log" is generated alongside the rest of the database files for this purpose.
+
+In the current version, only the classes used for file persistence, plus any error encountered while processing the .log file after an abnormal end, are logged.
+
+Note that the JDBC driver and the engine for 1.8.0 cannot be mixed with those of earlier versions in client/server setup. Check your classpaths and use the same version of the engine for both client and server.
+
+New property for larger data file limits is introduced. Once set, the limit will go up to 8GB. The property can be set with the following SQL command only when the database has no tables (new database).
+
+SET PROPERTY "hsqldb.cache_file_scale" 8
+
+To apply the change to an existing database, SHUTDOWN SCRIPT should be performed first, then the property=value line below should be added to the .properties file before reopening the database:
+
+hsqldb.cache_file_scale=8
+
+
+New property allows a CHECKPOINT DEFRAG to be performed automatically whenever CHECKPOINT is performed internally or via a user command.
+
+SET CHECKPOINT DEFRAG n
+
+The parameter n is the megabytes of abandoned space in the .data file. When a CHECKPOINT is performed either as a result of the .log file reaching the limit set by "SET LOGSIZE m", or by the user issuing a CHECKPOINT command, the amount of space abandoned during the session is checked and if it is larger than n, a CHECKPOINT DEFRAG is performed instead of a checkpoint.
+
+Rewrite of log and cache handling classes, including:
+New deleted block manager with more efficient deleted block reuse.
+Faster log processing after an abnormal termination.
+Better checks when maximum data file size is reached.
+Better recovery when maximum data file size is reached.
+
+Support for the res: connection protocol (database files in a jar) has been
+extended to allow CACHED tables.
+
+----------------
+
+JDBC AND OTHER ENHANCEMENTS
+
+ResultSetMetaData reports identical precision/scale in embedded and client/server modes
+
+When PreparedStatement.setTimestamp() and ResultSet.getTimestamp() are used with a Calendar parameter, the result is symmetrical if the time zones are equal.
+
+Added public shutdown() method to Server.
+
+Enhancements to DatabaseManagerSwing and SqlTool
+
+----------------
+
+BUG FIX
+
+Fixed bug where two indexes where switched, causing wrong results in some queries in the following circumstances:
+
+CREATE TABLE is executed.
+ALTER TABLE ADD FORIEGN KEY is used to create an FK on a different table that was already present when the first command was issued.
+CREATE INDEX is used to add an index.
+Data is added to the table.
+Database is shutdown.
+Database is restarted.
+At this point the indexes are switched and queries that use either of the indexes will not return the correct set of rows. If data is not added prior to the first shutdown, the database will works as normal.
+
+----------------
+
+UPGRADING DATABASES
+
+Databases that do not contain CACHED tables can be opened with the new version. For databases with CACHED tables, if they are created with versions 1.7.2 or 1.7.3, the SHUTDOWN SCRIPT command should be run once on the database prior to opening with the new version. For databases created with earlier versions, the instructions in the Advanced Topics section of The Guide should be followed.
+
+----------------
+
+OPEN OFFICE INTEGRATION
+
+When used in OpenOffice.org as the default database, several defaults and properties are set automatically:
+
+CREATE TABLE ... defaults to CREATE CACHED TABLE ...
+hsqldb.cache_scale=13
+hsqldb.cache_size_scale=8
+hsqldb.log_size=10
+SET WRITE DELAY 2
+sql.enforce_strict_size=true
+
+
+
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/databaseinjar.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/databaseinjar.txt
new file mode 100644
index 0000000..3383501
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/databaseinjar.txt
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+
+A patch for storing a readonly hsqldb database in a Jar was contributed by Brendan Ryan
+and has been incorporated into the code base. Additional work on connection URL
+allow more uniform access to this feature.
+
+The steps required are as follows:
+
+Ensure the database does not contain CACHED or TEXT tables.
+Make the database radonly after a SHUTDOWN.
+Include the two database files *.properties and *.script in a directory in your Jar
+Access the database with the jdbc:hsqldb:res: protocol
+
+The relative location of the database as taken from the jdbc url is used.
+For example, if the url is specified as "jdbc:hsqldb:res:/testdata/felder"
+then the database is loaded from the "/testdata/" directory in the jar
+and the database file names are "felder.properties" and
+felder.script" in that directory.
+
+Brendan Ryan wrote (text and sample changed):
+
+I have made a small change to allow a readonly hsqldb database (.script and
+.properties) to be stored in a JAR file so that it can be used with JWS.
+
+A sample jnlp file is given below.
+
+I hope the code is useful for someone.
+
+Regards
+Brendan Ryan
+-->
+
+<jnlp spec="1.0+" codebase="file:///c:/ERM/internet/build/pass/">
+<information>
+ <title>Mask Builder</title>
+ <vendor>PUI</vendor>
+ <homepage href="http://www.pi-ag.com" />
+ <description>Demonstration of JNLP</description>
+ <icon href="raptor.gif"/>
+</information>
+<offline-allowed/>
+<security>
+ <all-permissions/>
+</security>
+<resources>
+ <j2se version="1.4+" />
+ <jar href="pass-maskbuilder.jar"/>
+ <jar href="jaxb-rt-1.0-ea.jar"/>
+ <jar href="hsqldb.jar"/>
+ <jar href="testdb.jar"/>
+ <property name="jdbc.drivers" value="org.hsqldb.jdbcDriver"/>
+ <property name="jdbc.url" value="jdbc:hsqldb:res:/testdata/felder"/>
+ <property name="jdbc.user" value="sa"/>
+ <property name="jdbc.password" value="" />
+</resources>
+<application-desc />
+</jnlp>
+
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlFindFile.html b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlFindFile.html
new file mode 100644
index 0000000..55f34af
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlFindFile.html
@@ -0,0 +1,29 @@
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
+<title>HSQLDB Find File Sample Application</title>
+</head>
+<body bgcolor=#FFFFFF lang=EN-GB class="Normal">
+<h2>HSQLDB Find File Sample Application</h2>
+<p>This application builds a database of a directory tree and allows you to search
+ the database.</p>
+<p>This example application is designed for programmers who are new to the JDBC.
+ The functionality is kept low, so it should be easy to understand what is going
+ on. It connects, execute queries and inserts data into the database. </p>
+<p>First, the database must be initialized with a path. All the file names in
+ this directory and all its subdirectories will be stored in the database. After
+ this is done, the database can be searched for files that match a specific pattern.
+</p>
+<p>This sample application is not compiled as part of the hsqldb jar. You should
+ compile it yourself. You should modify the following examples to include the
+ correct location of the hsqldb.jar in the commands. </p>
+<h4>Usage</h4>
+<p>Re-create database from directory '.': </p>
+<p><code><span style='font-size:10.0pt;font-family:"Courier New"'>java -classpath
+ hsqldb.jar org.hsqldb.sample.FindFile -init .</span></code> </p>
+<p>Find files like 'name': </p>
+<p><code><span style='font-size:10.0pt;font-family:"Courier New"'>java -classpath
+ hsqldb.jar org.hsqldb.sample.FindFile name</span></code> </p>
+<p><font size="-1">This text is based on HypersonicSQL documentation, updated to reflect the latest version of HSQLDB</font></p>
+</body>
+</html>
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlSoftwareLinks.html b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlSoftwareLinks.html
new file mode 100644
index 0000000..f545bfb
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqlSoftwareLinks.html
@@ -0,0 +1,36 @@
+<HTML>
+<h3>ANNOUNCEMENTS OF SOME ADDITIONAL SOFTWARE THAT CAN POSSIBLY BE USED WITH HSQLDB</h3>
+<p>&nbsp;</p>
+<p>This document is a compilation of some information that has been submitted to HSQLDB mailing lists or forums. The HSQLDB project or its developers are not responsible for the software mentioned in this document, its suitability for any purpose, or the accuracy of the information provided in this document.</p>
+<hr>
+<p>LightCrypto is a set of Open Source Java<br>
+ classes with basic cryptographic routines using the BouncyCastle lightweight API.</p>
+<p>It uses a minimal amount of memory so it can be used with J2ME, browser applets, on small Java devices such as PDA's or Java enabled mobile phones or in any other situation where Sun's JCE (Java Cryptographic<br>
+ Extensions) is too heavy for the job.</p>
+<p>Hsqldb-ready functions are also included.</p>
+<p>Feature list:</p>
+<p># Create digest from strings and files with MD5 (default), SHA-1, SHA-256 , SHA-512 or RIPEMD160 hash algorithms<br>
+ # Encrypt/Decrypt strings and files using the AES (lightweight implementation) algorithm with any keylength (default 128 bits) in CBC mode with PKCS12 padding.<br>
+ # Encrypts the symmetric keystore and protects it with a passphrase (PBE)<br>
+ # Functions to hash/encrypt/decrypt data in HSQLDB embeddable database engine using SQL statements.<br>
+ # Open Source<br>
+ # 100% Java<br>
+ # Uses the BouncyCastle.org lightweight API instead of Sun's JCE (Java Cryptographic Extensions)</p>
+<p>Homepage: <a href="http://jcetaglib.sourceforge.net/lightcrypto/">http://jcetaglib.sourceforge.net/lightcrypto/</a></p>
+<p>Beta 1 (including HSqldb routines + examples) has been released and can be downloaded on<br>
+ <a href="http://sourceforge.net/project/showfiles.php?group_id=60642">http://sourceforge.net/project/showfiles.php?group_id=60642</a></p>
+<hr>
+<p>Open source, lightweight cryptography extensions to Java for use with LightCrypto or HSQLDB for SSL access can be found here:</p>
+<p><a href="http://www.bouncycastle.org/">http://www.bouncycastle.org/</a></p>
+<hr>
+<p>The open-source FormattedDataSet may be the easiest way to generate dynamic text such as HTML, and XML. </p>
+<p>I just deployed a demo WAR that allows developers to enter any hsqldb join and render the results as an HTML table that can be sorted by clicking on the column headers. I picked hsqldb for my database as I didn't want anyone that installed the war to have to worry about installing a database. </p>
+<p>The demo also times opening/closing Connections, ResultSets and Statements. This WAR would be useful for you guys to give out to demonstrate your database.</p>
+<p>The demo works with any RDBMS. </p>
+<p>Check it out at <a href="http://www.fdsapi.com">http://www.fdsapi.com</a> and select the live demo link.</p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+
+
+</HTML>
+
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqldb_lic.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqldb_lic.txt
new file mode 100644
index 0000000..953bfa0
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/hsqldb_lic.txt
@@ -0,0 +1,31 @@
+/* Copyright (c) 2001-2005, The HSQL Development Group
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * Redistributions of source code must retain the above copyright notice, this
+ * list of conditions and the following disclaimer.
+ *
+ * Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * Neither the name of the HSQL Development Group nor the names of its
+ * contributors may be used to endorse or promote products derived from this
+ * software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG,
+ * OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+ * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+ * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/hypersonic_lic.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/hypersonic_lic.txt
new file mode 100644
index 0000000..014bf60
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/hypersonic_lic.txt
@@ -0,0 +1,66 @@
+/* Copyright (c) 1995-2000, The Hypersonic SQL Group.
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * Redistributions of source code must retain the above copyright notice, this
+ * list of conditions and the following disclaimer.
+ *
+ * Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * Neither the name of the Hypersonic SQL Group nor the names of its
+ * contributors may be used to endorse or promote products derived from this
+ * software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL THE HYPERSONIC SQL GROUP,
+ * OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+ * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+ * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ *
+ * This software consists of voluntary contributions made by many individuals
+ * on behalf of the Hypersonic SQL Group.
+ *
+ *
+ * For work added by the HSQL Development Group:
+ *
+ * Copyright (c) 2001-2004, The HSQL Development Group
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * Redistributions of source code must retain the above copyright notice, this
+ * list of conditions and the following disclaimer.
+ *
+ * Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * Neither the name of the HSQL Development Group nor the names of its
+ * contributors may be used to endorse or promote products derived from this
+ * software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG,
+ * OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+ * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+ * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/readme-docauthors.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme-docauthors.txt
new file mode 100644
index 0000000..a3418bd
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme-docauthors.txt
@@ -0,0 +1,115 @@
+HOW TO CREATE AND WORK WITH DOCBOOK DOCUMENTS FOR HSQLDB
+
+At some point, this document itself should be converted to DocBook format.
+
+
+Our DocBook strategy is still subject to change. For now...
+
+
+TO CREATE A NEW DOCBOOK BOOK
+
+Think up a base filename for your document.
+It should be nice and short, without funny characters (but hyphens, other
+than leading hypends, are ok). Example: sqltool.
+Hereafter, I'll refer to this as your "book name".
+
+Create a subdirectory of "docsrc" with name of your book name.
+I'll refer to this directory (docsrc + book name) as "your book directory".
+
+Inside your book directory, create your main DocBook source file with name
+of your book name + ".xml", e.g. "sqltool.xml".
+
+Your DocBook document may reference or include shared files in the
+main 'docsrc' directory as well as any files which you put into your
+book directory.
+You may want to include sample .java files, screen shots, or component
+DocBook source files.
+Usually you will just copy these files right into your book directory.
+
+For examples of just about everything, see .../docsrc/sqltool/sqltool.xml.
+Notice that sqltool.xml pulls in a document section from the main docsrc
+directory.
+
+Add your book name to the .cvsignore file in the doc directory.
+
+Until all of the CVS artifacts are moved out of the "doc" directory,
+you will need to edit the clean-doc target in the build.xml file in
+the build directory so that it will remove the derived files for
+your book from under the doc directory.
+
+
+HOW TO REFERENCE OR INCLUDE OTHER FILES IN YOUR DOCBOOK SOURCE FILE(s).
+
+To link to outside documents (which you supply or not), you'll usually
+use the DocBook <ulink> element.
+
+To "import" other documents, just use the general external parsed entity
+mechanism.
+This is a basic DTD-style XML feature where you use macros like
+&entityname;. Either find an XML reference or look around our existing
+DocBook source files for an example to follow.
+
+One tricky point is how to include external files verbatim.
+If you just read in external files as parsed entities, they will be parsed
+as DocBook source (and therefore they must consist of, at least, legal
+XML)*.
+But often you will want to import a real, working file (like a
+configuration file, sql file, Java source file), and you won't want to
+hack it up just so you can import it.
+(For one thing, you shouldn't have to; for another, you may want to
+provide a link to the file for download, so you wouldn't want people
+to download a hacked-up version).
+It would be nice if you could CDATA, then include the entity, but that
+won't work since the &...; inclusion directive would thereby be escaped.
+If you don't know what the hell CDATA is, just follow the instructions
+in the next paragraph.
+
+To import a document verbatim, define an external parsed entity for
+the file ../../docwork/BOOKNAME/cdata/file.name, where BOOKNAME is
+your book name and file.name is the name of the file to be imported
+(which resides in the current directory).
+If you want to know, what will happen is, the Ant build will copy the
+file-to-be-imported to the directory .../docwork/BOOKNAME/cdata and will
+sandwich it in a CDATA directive.
+If you want to provide a link to the document, you just ulink to
+the document in the current directory, not to the one in the cdata
+
+POSTNOTE: The long-term way to do this is with XInclude, or some
+other generic XML inclusion mechanism. Unfortunately, none of the
+good methods work with the Java ports of DocBook!
+
+
+=======================================================================
+
+CONVENTIONS
+
+Please use <remark> elements to mark up notes for yourself or for
+other developers.
+All <remark>s should be removed before the doc goes public!
+
+Please capitalize HSQLDB like "Hsqldb" in titles, and capitalize like
+"HSQLDB" elsewhere. (In filepaths and package names you code as
+required for the filepath or package name, of course).
+
+=======================================================================
+
+TIPS
+
+When closing DocBook <screen> and <programlisting> elements, make
+sure that there is no line break after the text to display and before
+the closing </screen> or </programlisting> tag.
+Otherwise the resultant display will not look right.
+
+Don't capitalize words or phrases to emphasize them (including in
+section titles or headings).
+If you want to emphasize something a certain way, then use a DocBook
+emphasis role, and leave the presentation decisions to the style sheets.
+It is very easy to set a CSS style to capitalize headings if you want
+them to appear that way.
+
+
+
+* Theoretically it would be better and SHOULD be simpler to use
+unparsed entities for this purpose, but unparsed entities are a
+messy legacy feature of DTD which is more convoluted than the
+strategy described here.
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/readme.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme.txt
new file mode 100644
index 0000000..87f934c
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme.txt
@@ -0,0 +1,4 @@
+Readme FileAugust 2007
+ This package contains HSQLDB 1.8.0.8
+
+HSQLDB is a relational database engine and a set of tools written in Java.The file index.html in this directory contains the list of directories with their contents.Documentation and license information can be found in the /doc directory.Project home page: http://hsqldb.orgPlease check the site periodically for updated versions.
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/lib/readme_linux.txt b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme_linux.txt
new file mode 100644
index 0000000..6a435d9
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/lib/readme_linux.txt
@@ -0,0 +1,12 @@
+Readme Linux
+
+$Id$
+Query CVS for revision history.
+
+It is recommended to run the shell scripts(from /bin and /demo) from the
+console, as you will not to be able see any messages from the desktop.
+You should set the env variable $JAVA_HOME before running any of the sripts,
+or you can use the -jdkhome switch instead to specify the JDK.
+
+See the UNIX Quick Start chapter of the Hsqldb User Guide about how to use
+the UNIX init script 'hsqldb'.
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/license.html b/plugins/org.eclipse.net4j.db.hsqldb/license.html
new file mode 100644
index 0000000..d7b88e9
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/license.html
@@ -0,0 +1,319 @@
+<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"><head>
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<meta name="ProgId" content="Word.Document">
+<meta name="Generator" content="Microsoft Word 9">
+<meta name="Originator" content="Microsoft Word 9">
+<link rel="File-List" href="http://www.eclipse.org/org/documents/Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml"><title>Eclipse Public License - Version 1.0</title><!--[if gte mso 9]><xml>
+ <o:DocumentProperties>
+ <o:Revision>2</o:Revision>
+ <o:TotalTime>3</o:TotalTime>
+ <o:Created>2004-03-05T23:03:00Z</o:Created>
+ <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
+ <o:Pages>4</o:Pages>
+ <o:Words>1626</o:Words>
+ <o:Characters>9270</o:Characters>
+ <o:Lines>77</o:Lines>
+ <o:Paragraphs>18</o:Paragraphs>
+ <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
+ <o:Version>9.4402</o:Version>
+ </o:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+ <w:TrackRevisions/>
+ </w:WordDocument>
+</xml><![endif]-->
+
+
+<style>
+<!--
+ /* Font Definitions */
+@font-face
+ {font-family:Tahoma;
+ panose-1:2 11 6 4 3 5 4 4 2 4;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:553679495 -2147483648 8 0 66047 0;}
+ /* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {mso-style-parent:"";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p
+ {margin-right:0in;
+ mso-margin-top-alt:auto;
+ mso-margin-bottom-alt:auto;
+ margin-left:0in;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p.BalloonText, li.BalloonText, div.BalloonText
+ {mso-style-name:"Balloon Text";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:8.0pt;
+ font-family:Tahoma;
+ mso-fareast-font-family:"Times New Roman";}
+@page Section1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.25in 1.0in 1.25in;
+ mso-header-margin:.5in;
+ mso-footer-margin:.5in;
+ mso-paper-source:0;}
+div.Section1
+ {page:Section1;}
+-->
+</style></head>
+
+<body style="" lang="EN-US">
+
+<div class="Section1">
+
+<p style="text-align: center;" align="center"><b>Eclipse Public License - v 1.0</b>
+</p>
+
+<p><span style="font-size: 10pt;">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
+THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
+REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
+OF THIS AGREEMENT.</span> </p>
+
+<p><b><span style="font-size: 10pt;">1. DEFINITIONS</span></b> </p>
+
+<p><span style="font-size: 10pt;">"Contribution" means:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and<br clear="left">
+b) in the case of each subsequent Contributor:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+changes to the Program, and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+additions to the Program;</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">where
+such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution 'originates' from a Contributor
+if it was added to the Program by such Contributor itself or anyone acting on
+such Contributor's behalf. Contributions do not include additions to the
+Program which: (i) are separate modules of software distributed in conjunction
+with the Program under their own license agreement, and (ii) are not derivative
+works of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Contributor" means any person or
+entity that distributes the Program.</span> </p>
+
+<p><span style="font-size: 10pt;">"Licensed Patents " mean patent
+claims licensable by a Contributor which are necessarily infringed by the use
+or sale of its Contribution alone or when combined with the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Program" means the Contributions
+distributed in accordance with this Agreement.</span> </p>
+
+<p><span style="font-size: 10pt;">"Recipient" means anyone who
+receives the Program under this Agreement, including all Contributors.</span> </p>
+
+<p><b><span style="font-size: 10pt;">2. GRANT OF RIGHTS</span></b> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+Subject to the terms of this Agreement, each Contributor hereby grants Recipient
+a non-exclusive, worldwide, royalty-free copyright license to<span style="color: red;"> </span>reproduce, prepare derivative works of, publicly
+display, publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and object code
+form.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide,<span style="color: green;"> </span>royalty-free
+patent license under Licensed Patents to make, use, sell, offer to sell, import
+and otherwise transfer the Contribution of such Contributor, if any, in source
+code and object code form. This patent license shall apply to the combination
+of the Contribution and the Program if, at the time the Contribution is added
+by the Contributor, such addition of the Contribution causes such combination
+to be covered by the Licensed Patents. The patent license shall not apply to
+any other combinations which include the Contribution. No hardware per se is
+licensed hereunder. </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">c)
+Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor
+that the Program does not infringe the patent or other intellectual property
+rights of any other entity. Each Contributor disclaims any liability to Recipient
+for claims brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the rights and
+licenses granted hereunder, each Recipient hereby assumes sole responsibility
+to secure any other intellectual property rights needed, if any. For example,
+if a third party patent license is required to allow Recipient to distribute
+the Program, it is Recipient's responsibility to acquire that license before
+distributing the Program.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">d)
+Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in
+this Agreement. </span></p>
+
+<p><b><span style="font-size: 10pt;">3. REQUIREMENTS</span></b> </p>
+
+<p><span style="font-size: 10pt;">A Contributor may choose to distribute the
+Program in object code form under its own license agreement, provided that:</span>
+</p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it complies with the terms and conditions of this Agreement; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+its license agreement:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title
+and non-infringement, and implied warranties or conditions of merchantability
+and fitness for a particular purpose; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such
+as lost profits; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iii)
+states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iv)
+states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a
+medium customarily used for software exchange.<span style="color: blue;"> </span></span></p>
+
+<p><span style="font-size: 10pt;">When the Program is made available in source
+code form:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it must be made available under this Agreement; and </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b) a
+copy of this Agreement must be included with each copy of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Contributors may not remove or alter any
+copyright notices contained within the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Each Contributor must identify itself as the
+originator of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution. </span></p>
+
+<p><b><span style="font-size: 10pt;">4. COMMERCIAL DISTRIBUTION</span></b> </p>
+
+<p><span style="font-size: 10pt;">Commercial distributors of software may
+accept certain responsibilities with respect to end users, business partners
+and the like. While this license is intended to facilitate the commercial use
+of the Program, the Contributor who includes the Program in a commercial
+product offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial
+Contributor") hereby agrees to defend and indemnify every other
+Contributor ("Indemnified Contributor") against any losses, damages and
+costs (collectively "Losses") arising from claims, lawsuits and other
+legal actions brought by a third party against the Indemnified Contributor to
+the extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor
+to control, and cooperate with the Commercial Contributor in, the defense and
+any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.</span> </p>
+
+<p><span style="font-size: 10pt;">For example, a Contributor might include the
+Program in a commercial product offering, Product X. That Contributor is then a
+Commercial Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance claims and
+warranties are such Commercial Contributor's responsibility alone. Under this
+section, the Commercial Contributor would have to defend claims against the
+other Contributors related to those performance claims and warranties, and if a
+court requires any other Contributor to pay any damages as a result, the
+Commercial Contributor must pay those damages.</span> </p>
+
+<p><b><span style="font-size: 10pt;">5. NO WARRANTY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
+WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
+MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and distributing the
+Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or
+equipment, and unavailability or interruption of operations. </span></p>
+
+<p><b><span style="font-size: 10pt;">6. DISCLAIMER OF LIABILITY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
+THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
+
+<p><b><span style="font-size: 10pt;">7. GENERAL</span></b> </p>
+
+<p><span style="font-size: 10pt;">If any provision of this Agreement is invalid
+or unenforceable under applicable law, it shall not affect the validity or
+enforceability of the remainder of the terms of this Agreement, and without
+further action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.</span> </p>
+
+<p><span style="font-size: 10pt;">If Recipient institutes patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Program itself (excluding combinations of the Program with
+other software or hardware) infringes such Recipient's patent(s), then such
+Recipient's rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed. </span></p>
+
+<p><span style="font-size: 10pt;">All Recipient's rights under this Agreement
+shall terminate if it fails to comply with any of the material terms or
+conditions of this Agreement and does not cure such failure in a reasonable
+period of time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use and
+distribution of the Program as soon as reasonably practicable. However,
+Recipient's obligations under this Agreement and any licenses granted by
+Recipient relating to the Program shall continue and survive. </span></p>
+
+<p><span style="font-size: 10pt;">Everyone is permitted to copy and distribute
+copies of this Agreement, but in order to avoid inconsistency the Agreement is
+copyrighted and may only be modified in the following manner. The Agreement
+Steward reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement Steward has
+the right to modify this Agreement. The Eclipse Foundation is the initial
+Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version
+of the Agreement will be given a distinguishing version number. The Program
+(including Contributions) may always be distributed subject to the version of
+the Agreement under which it was received. In addition, after a new version of
+the Agreement is published, Contributor may elect to distribute the Program
+(including its Contributions) under the new version. Except as expressly stated
+in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
+the intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.</span> </p>
+
+<p><span style="font-size: 10pt;">This Agreement is governed by the laws of the
+State of New York and the intellectual property laws of the United States of
+America. No party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each party waives
+its rights to a jury trial in any resulting litigation.</span> </p>
+
+<p class="MsoNormal"><!--[if !supportEmptyParas]-->&nbsp;<!--[endif]--><o:p></o:p></p>
+
+</div>
+
+</body></html> \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/HSQLDBAdapter.java b/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/HSQLDBAdapter.java
new file mode 100644
index 0000000..0585e58
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/HSQLDBAdapter.java
@@ -0,0 +1,34 @@
+/***************************************************************************
+ * Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Eike Stepper - initial API and implementation
+ **************************************************************************/
+package org.eclipse.net4j.db.internal.hsqldb;
+
+import org.eclipse.net4j.internal.db.DBAdapter;
+
+import org.hsqldb.jdbcDriver;
+
+import java.sql.Driver;
+import java.util.Arrays;
+
+/**
+ * @author Eike Stepper
+ */
+public class HSQLDBAdapter extends DBAdapter
+{
+ public HSQLDBAdapter()
+ {
+ super("hsqldb", "1.8.0.8");
+ }
+
+ public Driver getJDBCDriver()
+ {
+ return new jdbcDriver();
+ }
+}
diff --git a/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/bundle/OM.java b/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/bundle/OM.java
new file mode 100644
index 0000000..4a4bd8d
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.hsqldb/src/org/eclipse/net4j/db/internal/hsqldb/bundle/OM.java
@@ -0,0 +1,44 @@
+/***************************************************************************
+ * Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Eike Stepper - initial API and implementation
+ **************************************************************************/
+package org.eclipse.net4j.db.internal.hsqldb.bundle;
+
+import org.eclipse.net4j.util.om.OMBundle;
+import org.eclipse.net4j.util.om.OMPlatform;
+import org.eclipse.net4j.util.om.OSGiActivator;
+import org.eclipse.net4j.util.om.log.OMLogger;
+import org.eclipse.net4j.util.om.trace.OMTracer;
+
+/**
+ * @author Eike Stepper
+ */
+public abstract class OM
+{
+ public static final String BUNDLE_ID = "org.eclipse.net4j.db.hsqldb"; //$NON-NLS-1$
+
+ public static final OMBundle BUNDLE = OMPlatform.INSTANCE.bundle(BUNDLE_ID, OM.class);
+
+ public static final OMTracer DEBUG = BUNDLE.tracer("debug"); //$NON-NLS-1$
+
+ public static final OMTracer DEBUG_SQL = DEBUG.tracer("sql"); //$NON-NLS-1$
+
+ public static final OMLogger LOG = BUNDLE.logger();
+
+ /**
+ * @author Eike Stepper
+ */
+ public static final class Activator extends OSGiActivator
+ {
+ public Activator()
+ {
+ super(BUNDLE);
+ }
+ }
+}
diff --git a/plugins/org.eclipse.net4j.db.mysql/.classpath b/plugins/org.eclipse.net4j.db.mysql/.classpath
new file mode 100644
index 0000000..8d206e4
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/.classpath
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry exported="true" kind="lib" path="lib/mysql-connector-java-5.1.5-bin.jar"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
diff --git a/plugins/org.eclipse.net4j.db.mysql/.cvsignore b/plugins/org.eclipse.net4j.db.mysql/.cvsignore
new file mode 100644
index 0000000..ba077a4
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/.cvsignore
@@ -0,0 +1 @@
+bin
diff --git a/plugins/org.eclipse.net4j.db.mysql/.options b/plugins/org.eclipse.net4j.db.mysql/.options
new file mode 100644
index 0000000..f51f13b
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/.options
@@ -0,0 +1,4 @@
+# Debugging and tracing options
+
+org.eclipse.net4j.db.mysql/debug = true
+org.eclipse.net4j.db.mysql/debug.sql = true
diff --git a/plugins/org.eclipse.net4j.db.mysql/.project b/plugins/org.eclipse.net4j.db.mysql/.project
new file mode 100644
index 0000000..306afc0
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/.project
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.net4j.db.mysql</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
diff --git a/plugins/org.eclipse.net4j.db.mysql/META-INF/MANIFEST.MF b/plugins/org.eclipse.net4j.db.mysql/META-INF/MANIFEST.MF
new file mode 100644
index 0000000..366f46e
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/META-INF/MANIFEST.MF
@@ -0,0 +1,13 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.eclipse.net4j.db.mysql;singleton:=true
+Bundle-Version: 0.8.0.qualifier
+Bundle-Vendor: %providerName
+Bundle-Localization: fragment
+Bundle-ClassPath: .,
+ lib/mysql-connector-java-5.1.5-bin.jar
+Fragment-Host: org.eclipse.net4j.db;bundle-version="[0.8.0,0.9.0)"
+Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.3.0,4.0.0)"
+Export-Package: org.eclipse.net4j.db.internal.mysql;version="0.8.0",
+ org.gjt.mm.mysql;x-friends:="org.eclipse.emf.cdo.tests,org.eclipse.net4j.jms.tests,org.eclipse.net4j.tests"
diff --git a/plugins/org.eclipse.net4j.db.mysql/about.html b/plugins/org.eclipse.net4j.db.mysql/about.html
new file mode 100644
index 0000000..d35d5ae
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/about.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>June 5, 2007</p>
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;). Unless otherwise
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is available
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was
+provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org/">http://www.eclipse.org</a>.</p>
+
+</body>
+</html>
diff --git a/plugins/org.eclipse.net4j.db.mysql/build.properties b/plugins/org.eclipse.net4j.db.mysql/build.properties
new file mode 100644
index 0000000..c817fcf
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/build.properties
@@ -0,0 +1,24 @@
+# Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# Eike Stepper - initial API and implementation
+
+# NLS_MESSAGEFORMAT_VAR
+
+source.. = src/
+output.. = bin/
+bin.includes = META-INF/,\
+ .,\
+ about.html,\
+ .options,\
+ copyright.txt,\
+ epl-v10.html,\
+ license.html,\
+ fragment.properties,\
+ fragment.xml,\
+ lib/,\
+ lib/mysql-connector-java-5.1.5-bin.jar
diff --git a/plugins/org.eclipse.net4j.db.mysql/copyright.txt b/plugins/org.eclipse.net4j.db.mysql/copyright.txt
new file mode 100644
index 0000000..025f152
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/copyright.txt
@@ -0,0 +1,8 @@
+Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+All rights reserved. This program and the accompanying materials
+are made available under the terms of the Eclipse Public License v1.0
+which accompanies this distribution, and is available at
+http://www.eclipse.org/legal/epl-v10.html
+
+Contributors:
+ Eike Stepper - initial API and implementation \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.mysql/epl-v10.html b/plugins/org.eclipse.net4j.db.mysql/epl-v10.html
new file mode 100644
index 0000000..d7b88e9
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/epl-v10.html
@@ -0,0 +1,319 @@
+<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"><head>
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<meta name="ProgId" content="Word.Document">
+<meta name="Generator" content="Microsoft Word 9">
+<meta name="Originator" content="Microsoft Word 9">
+<link rel="File-List" href="http://www.eclipse.org/org/documents/Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml"><title>Eclipse Public License - Version 1.0</title><!--[if gte mso 9]><xml>
+ <o:DocumentProperties>
+ <o:Revision>2</o:Revision>
+ <o:TotalTime>3</o:TotalTime>
+ <o:Created>2004-03-05T23:03:00Z</o:Created>
+ <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
+ <o:Pages>4</o:Pages>
+ <o:Words>1626</o:Words>
+ <o:Characters>9270</o:Characters>
+ <o:Lines>77</o:Lines>
+ <o:Paragraphs>18</o:Paragraphs>
+ <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
+ <o:Version>9.4402</o:Version>
+ </o:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+ <w:TrackRevisions/>
+ </w:WordDocument>
+</xml><![endif]-->
+
+
+<style>
+<!--
+ /* Font Definitions */
+@font-face
+ {font-family:Tahoma;
+ panose-1:2 11 6 4 3 5 4 4 2 4;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:553679495 -2147483648 8 0 66047 0;}
+ /* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {mso-style-parent:"";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p
+ {margin-right:0in;
+ mso-margin-top-alt:auto;
+ mso-margin-bottom-alt:auto;
+ margin-left:0in;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p.BalloonText, li.BalloonText, div.BalloonText
+ {mso-style-name:"Balloon Text";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:8.0pt;
+ font-family:Tahoma;
+ mso-fareast-font-family:"Times New Roman";}
+@page Section1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.25in 1.0in 1.25in;
+ mso-header-margin:.5in;
+ mso-footer-margin:.5in;
+ mso-paper-source:0;}
+div.Section1
+ {page:Section1;}
+-->
+</style></head>
+
+<body style="" lang="EN-US">
+
+<div class="Section1">
+
+<p style="text-align: center;" align="center"><b>Eclipse Public License - v 1.0</b>
+</p>
+
+<p><span style="font-size: 10pt;">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
+THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
+REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
+OF THIS AGREEMENT.</span> </p>
+
+<p><b><span style="font-size: 10pt;">1. DEFINITIONS</span></b> </p>
+
+<p><span style="font-size: 10pt;">"Contribution" means:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and<br clear="left">
+b) in the case of each subsequent Contributor:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+changes to the Program, and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+additions to the Program;</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">where
+such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution 'originates' from a Contributor
+if it was added to the Program by such Contributor itself or anyone acting on
+such Contributor's behalf. Contributions do not include additions to the
+Program which: (i) are separate modules of software distributed in conjunction
+with the Program under their own license agreement, and (ii) are not derivative
+works of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Contributor" means any person or
+entity that distributes the Program.</span> </p>
+
+<p><span style="font-size: 10pt;">"Licensed Patents " mean patent
+claims licensable by a Contributor which are necessarily infringed by the use
+or sale of its Contribution alone or when combined with the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Program" means the Contributions
+distributed in accordance with this Agreement.</span> </p>
+
+<p><span style="font-size: 10pt;">"Recipient" means anyone who
+receives the Program under this Agreement, including all Contributors.</span> </p>
+
+<p><b><span style="font-size: 10pt;">2. GRANT OF RIGHTS</span></b> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+Subject to the terms of this Agreement, each Contributor hereby grants Recipient
+a non-exclusive, worldwide, royalty-free copyright license to<span style="color: red;"> </span>reproduce, prepare derivative works of, publicly
+display, publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and object code
+form.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide,<span style="color: green;"> </span>royalty-free
+patent license under Licensed Patents to make, use, sell, offer to sell, import
+and otherwise transfer the Contribution of such Contributor, if any, in source
+code and object code form. This patent license shall apply to the combination
+of the Contribution and the Program if, at the time the Contribution is added
+by the Contributor, such addition of the Contribution causes such combination
+to be covered by the Licensed Patents. The patent license shall not apply to
+any other combinations which include the Contribution. No hardware per se is
+licensed hereunder. </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">c)
+Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor
+that the Program does not infringe the patent or other intellectual property
+rights of any other entity. Each Contributor disclaims any liability to Recipient
+for claims brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the rights and
+licenses granted hereunder, each Recipient hereby assumes sole responsibility
+to secure any other intellectual property rights needed, if any. For example,
+if a third party patent license is required to allow Recipient to distribute
+the Program, it is Recipient's responsibility to acquire that license before
+distributing the Program.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">d)
+Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in
+this Agreement. </span></p>
+
+<p><b><span style="font-size: 10pt;">3. REQUIREMENTS</span></b> </p>
+
+<p><span style="font-size: 10pt;">A Contributor may choose to distribute the
+Program in object code form under its own license agreement, provided that:</span>
+</p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it complies with the terms and conditions of this Agreement; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+its license agreement:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title
+and non-infringement, and implied warranties or conditions of merchantability
+and fitness for a particular purpose; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such
+as lost profits; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iii)
+states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iv)
+states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a
+medium customarily used for software exchange.<span style="color: blue;"> </span></span></p>
+
+<p><span style="font-size: 10pt;">When the Program is made available in source
+code form:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it must be made available under this Agreement; and </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b) a
+copy of this Agreement must be included with each copy of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Contributors may not remove or alter any
+copyright notices contained within the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Each Contributor must identify itself as the
+originator of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution. </span></p>
+
+<p><b><span style="font-size: 10pt;">4. COMMERCIAL DISTRIBUTION</span></b> </p>
+
+<p><span style="font-size: 10pt;">Commercial distributors of software may
+accept certain responsibilities with respect to end users, business partners
+and the like. While this license is intended to facilitate the commercial use
+of the Program, the Contributor who includes the Program in a commercial
+product offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial
+Contributor") hereby agrees to defend and indemnify every other
+Contributor ("Indemnified Contributor") against any losses, damages and
+costs (collectively "Losses") arising from claims, lawsuits and other
+legal actions brought by a third party against the Indemnified Contributor to
+the extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor
+to control, and cooperate with the Commercial Contributor in, the defense and
+any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.</span> </p>
+
+<p><span style="font-size: 10pt;">For example, a Contributor might include the
+Program in a commercial product offering, Product X. That Contributor is then a
+Commercial Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance claims and
+warranties are such Commercial Contributor's responsibility alone. Under this
+section, the Commercial Contributor would have to defend claims against the
+other Contributors related to those performance claims and warranties, and if a
+court requires any other Contributor to pay any damages as a result, the
+Commercial Contributor must pay those damages.</span> </p>
+
+<p><b><span style="font-size: 10pt;">5. NO WARRANTY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
+WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
+MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and distributing the
+Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or
+equipment, and unavailability or interruption of operations. </span></p>
+
+<p><b><span style="font-size: 10pt;">6. DISCLAIMER OF LIABILITY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
+THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
+
+<p><b><span style="font-size: 10pt;">7. GENERAL</span></b> </p>
+
+<p><span style="font-size: 10pt;">If any provision of this Agreement is invalid
+or unenforceable under applicable law, it shall not affect the validity or
+enforceability of the remainder of the terms of this Agreement, and without
+further action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.</span> </p>
+
+<p><span style="font-size: 10pt;">If Recipient institutes patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Program itself (excluding combinations of the Program with
+other software or hardware) infringes such Recipient's patent(s), then such
+Recipient's rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed. </span></p>
+
+<p><span style="font-size: 10pt;">All Recipient's rights under this Agreement
+shall terminate if it fails to comply with any of the material terms or
+conditions of this Agreement and does not cure such failure in a reasonable
+period of time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use and
+distribution of the Program as soon as reasonably practicable. However,
+Recipient's obligations under this Agreement and any licenses granted by
+Recipient relating to the Program shall continue and survive. </span></p>
+
+<p><span style="font-size: 10pt;">Everyone is permitted to copy and distribute
+copies of this Agreement, but in order to avoid inconsistency the Agreement is
+copyrighted and may only be modified in the following manner. The Agreement
+Steward reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement Steward has
+the right to modify this Agreement. The Eclipse Foundation is the initial
+Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version
+of the Agreement will be given a distinguishing version number. The Program
+(including Contributions) may always be distributed subject to the version of
+the Agreement under which it was received. In addition, after a new version of
+the Agreement is published, Contributor may elect to distribute the Program
+(including its Contributions) under the new version. Except as expressly stated
+in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
+the intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.</span> </p>
+
+<p><span style="font-size: 10pt;">This Agreement is governed by the laws of the
+State of New York and the intellectual property laws of the United States of
+America. No party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each party waives
+its rights to a jury trial in any resulting litigation.</span> </p>
+
+<p class="MsoNormal"><!--[if !supportEmptyParas]-->&nbsp;<!--[endif]--><o:p></o:p></p>
+
+</div>
+
+</body></html> \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.mysql/fragment.properties b/plugins/org.eclipse.net4j.db.mysql/fragment.properties
new file mode 100644
index 0000000..a749b09
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/fragment.properties
@@ -0,0 +1,25 @@
+# Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+# Eike Stepper - initial API and implementation
+
+# NLS_MESSAGEFORMAT_VAR
+
+# ==============================================================================
+# Do not change the properties between this line and the last line containing:
+# %%% END OF TRANSLATED PROPERTIES %%%
+# Instead, either redefine an existing property, or create a new property,
+# append it to the end of the file, and change the code to use the new name.
+# ==============================================================================
+
+pluginName = Net4j DB MYSQL (Incubation)
+providerName = Eclipse.org
+
+# ==============================================================================
+# %%% END OF TRANSLATED PROPERTIES %%%
+# The above properties have been shipped for translation.
+# ==============================================================================
diff --git a/plugins/org.eclipse.net4j.db.mysql/fragment.xml b/plugins/org.eclipse.net4j.db.mysql/fragment.xml
new file mode 100644
index 0000000..3613e91
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/fragment.xml
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.3"?>
+<!--
+ <copyright>
+
+ Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ All rights reserved. This program and the accompanying materials
+ are made available under the terms of the Eclipse Public License v1.0
+ which accompanies this distribution, and is available at
+ http://www.eclipse.org/legal/epl-v10.html
+
+ Contributors:
+ Eike Stepper - Initial API and implementation
+
+ </copyright>
+-->
+
+<plugin>
+
+ <extension
+ point="org.eclipse.net4j.db.dbAdapters">
+ <dbAdapter
+ class="org.eclipse.net4j.db.internal.mysql.MYSQLAdapter"
+ name="mysql"
+ version="5.1.5">
+ </dbAdapter>
+ </extension>
+
+</plugin>
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/.cvsignore b/plugins/org.eclipse.net4j.db.mysql/lib/.cvsignore
new file mode 100644
index 0000000..d392f0e
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/.cvsignore
@@ -0,0 +1 @@
+*.jar
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/CHANGES b/plugins/org.eclipse.net4j.db.mysql/lib/CHANGES
new file mode 100644
index 0000000..c0cbc52
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/CHANGES
@@ -0,0 +1,3753 @@
+# Changelog
+# $Id$
+10-09-07 - Version 5.1.5
+
+ - Released instead of 5.1.4 to pickup patch for BUG#31053
+ from 5.0.8.
+
+10-09-07 - Version 5.1.4
+
+ - Added "autoSlowLog" configuration property, overrides
+ "slowQueryThreshold*" properties, driver determines slow
+ queries by those that are slower than 5 * stddev of the mean
+ query time (outside the 96% percentile).
+
+ - Fixed BUG#28256 - When connection is in read-only mode,
+ queries that are wrapped in parentheses incorrectly identified
+ as DML.
+
+09-07-07 - Version 5.1.3 RC
+
+ - Setting "useBlobToStoreUTF8OutsideBMP" to "true" tells the
+ driver to treat [MEDIUM/LONG/TINY]BLOB columns as [LONG]VARCHAR
+ columns holding text encoded in UTF-8 that has characters
+ outside the BMP (4-byte encodings), which MySQL server
+ can't handle natively.
+
+ Set "utf8OutsideBmpExcludedColumnNamePattern" to a regex so that
+ column names matching the given regex will still be treated
+ as BLOBs The regex must follow the patterns used for the
+ java.util.regex package. The default is to exclude no columns,
+ and include all columns.
+
+ Set "utf8OutsideBmpIncludedColumnNamePattern" to specify exclusion
+ rules to "utf8OutsideBmpExcludedColumnNamePattern". The regex must
+ follow the patterns used for the java.util.regex package.
+
+ - New methods on com.mysql.jdbc.Statement: setLocalInfileInputStream()
+ and getLocalInfileInputStream().
+
+ setLocalInfileInputStream() sets an InputStream instance that will be used to send data
+ to the MySQL server for a "LOAD DATA LOCAL INFILE" statement
+ rather than a FileInputStream or URLInputStream that represents
+ the path given as an argument to the statement.
+
+ This stream will be read to completion upon execution of a
+ "LOAD DATA LOCAL INFILE" statement, and will automatically
+ be closed by the driver, so it needs to be reset
+ before each call to execute*() that would cause the MySQL
+ server to request data to fulfill the request for
+ "LOAD DATA LOCAL INFILE".
+
+ If this value is set to NULL, the driver will revert to using
+ a FileInputStream or URLInputStream as required.
+
+ getLocalInfileInputStream() returns the InputStream instance that will be used to send
+ data in response to a "LOAD DATA LOCAL INFILE" statement.
+
+ This method returns NULL if no such stream has been set
+ via setLocalInfileInputStream().
+
+ - The driver now connects with an initial character set
+ of "utf-8" solely for the purposes of authentication to
+ allow usernames and database names in any character set to
+ be used in the JDBC URL.
+
+ - Errors encountered during Statement/PreparedStatement/CallableStatement.executeBatch()
+ when "rewriteBatchStatements" has been set to "true" now return
+ BatchUpdateExceptions according to the setting of "continueBatchOnError".
+
+ If "continueBatchOnError" is set to "true", the update counts for the
+ "chunk" that were sent as one unit will all be set to EXECUTE_FAILED, but
+ the driver will attempt to process the remainder of the batch. You can determine which
+ "chunk" failed by looking at the update counts returned in the BatchUpdateException.
+
+ If "continueBatchOnError" is set to "false", the update counts returned
+ will contain the failed "chunk", and stop with the failed chunk, with all
+ counts for the failed "chunk" set to EXECUTE_FAILED.
+
+ Since MySQL doesn't return multiple error codes for multiple-statements, or
+ for multi-value INSERT/REPLACE, it is the application's responsibility to handle
+ determining which item(s) in the "chunk" actually failed.
+
+ - Statement.setQueryTimeout()s now affect the entire batch for batched
+ statements, rather than the individual statements that make up the batch.
+
+06-29-07 - Version 5.1.2 Beta
+
+ - Setting the configuration property "rewriteBatchedStatements"
+ to "true" will now cause the driver to rewrite batched prepared
+ statements with more than 3 parameter sets in a batch into
+ multi-statements (separated by ";") if they are not plain
+ (i.e. without SELECT or ON DUPLICATE KEY UPDATE clauses) INSERT
+ or REPLACE statements.
+
+06-22-07 - Version 5.1.1 Alpha
+
+ - Pulled vendor-extension methods of Connection implementation out
+ into an interface to support java.sql.Wrapper functionality from
+ ConnectionPoolDataSource. The vendor extensions are javadoc'd in
+ the com.mysql.jdbc.Connection interface.
+
+ For those looking further into the driver implementation, it is not
+ an API that is used for plugability of implementations inside our driver
+ (which is why there are still references to ConnectionImpl throughout the
+ code).
+
+ Incompatible change: Connection.serverPrepare(String) has been re-named
+ to Connection.serverPrepareStatement() for consistency with
+ Connection.clientPrepareStatement().
+
+ We've also added server and client prepareStatement() methods that cover
+ all of the variants in the JDBC API.
+
+ - Similar to Connection, we pulled out vendor extensions to Statement
+ into an interface named "com.mysql.Statement", and moved the Statement
+ class into com.mysql.StatementImpl. The two methods (javadoc'd in
+ "com.mysql.Statement" are enableStreamingResults(), which already existed,
+ and disableStreamingResults() which sets the statement instance back to
+ the fetch size and result set type it had before enableStreamingResults()
+ was called.
+
+ - Added experimental support for statement "interceptors" via the
+ com.mysql.jdbc.StatementInterceptor interface, examples are
+ in com/mysql/jdbc/interceptors.
+
+ Implement this interface to be placed "in between" query execution, so that
+ you can influence it. (currently experimental).
+
+ StatementInterceptors are "chainable" when configured by the user, the
+ results returned by the "current" interceptor will be passed on to the next
+ on in the chain, from left-to-right order, as specified by the user in the
+ JDBC configuration property "statementInterceptors".
+
+ See the sources (fully javadoc'd) for com.mysql.jdbc.StatementInterceptor
+ for more details until we iron out the API and get it documented in the
+ manual.
+
+ - Externalized the descriptions of connection properties.
+
+ - The data (and how it's stored) for ResultSet rows are now behind an
+ interface which allows us (in some cases) to allocate less memory
+ per row, in that for "streaming" result sets, we re-use the packet
+ used to read rows, since only one row at a time is ever active.
+
+ - Made it possible to retrieve prepared statement parameter bindings
+ (to be used in StatementInterceptors, primarily).
+
+ - Row navigation now causes any streams/readers open on the result set
+ to be closed, as in some cases we're reading directly from a shared network
+ packet and it will be overwritten by the "next" row.
+
+ - Setting "rewriteBatchedStatements" to "true" now causes CallableStatements
+ with batched arguments to be re-written in the form "CALL (...); CALL (...); ..."
+ to send the batch in as few client-server round trips as possible.
+
+ - Driver now picks appropriate internal row representation (whole row in one
+ buffer, or individual byte[]s for each column value) depending on heuristics,
+ including whether or not the row has BLOB or TEXT types and the overall
+ row-size. The threshold for row size that will cause the driver to
+ use a buffer rather than individual byte[]s is configured by the
+ configuration property "largeRowSizeThreshold", which has a default
+ value of 2KB.
+
+04-11-07 - Version 5.1.0 Alpha
+
+ - Bumped JDBC Specification version number in jar-file manifest.
+
+ - Re-worked Ant buildfile to build JDBC-4.0 classes separately, as well
+ as support building under Eclipse (since Eclipse can't mix/match JDKs).
+
+ To build, you must set JAVA_HOME to J2SDK-1.4.2 or Java-5, and set
+ the following properties on your Ant commandline:
+
+ com.mysql.jdbc.java6.javac - full path to your Java-6 javac executable
+ com.mysql.jdbc.java6.rtjar - full path to your Java-6 rt.jar file
+
+ - New feature - driver will automatically adjust session variable
+ "net_write_timeout" when it determines its been asked for a "streaming"
+ result, and resets it to the previous value when the result set
+ has been consumed. (configuration property is named
+ "netTimeoutForStreamingResults", value has unit of seconds,
+ the value '0' means the driver will not try and adjust this value).
+
+ - Added support for JDBC-4.0 categorized SQLExceptions.
+
+ - Refactored CommunicationsException into a JDBC3 version, and a JDBC4
+ version (which extends SQLRecoverableException, now that it exists).
+
+ This change means that if you were catching
+ com.mysql.jdbc.CommunicationsException in your applications instead
+ of looking at the SQLState class of "08", and are moving to Java 6
+ (or newer), you need to change your imports to that exception
+ to be com.mysql.jdbc.exceptions.jdbc4.CommunicationsException, as
+ the old class will not be instantiated for communications link-related
+ errors under Java 6.
+
+ - Added support for JDBC-4.0's client information. The backend storage
+ of information provided via Connection.setClientInfo() and retrieved
+ by Connection.getClientInfo() is pluggable by any class that implements
+ the com.mysql.jdbc.JDBC4ClientInfoProvider interface and has a no-args
+ constructor.
+
+ The implementation used by the driver is configured using the
+ "clientInfoProvider" configuration property (with a default of value
+ of "com.mysql.jdbc.JDBC4CommentClientInfoProvider", an implementation
+ which lists the client info as a comment prepended to every query
+ sent to the server).
+
+ This functionality is only available when using Java-6 or newer.
+
+ - Added support for JDBC-4.0's SQLXML interfaces.
+
+ - Added support for JDBC-4.0's Wrapper interface.
+
+ - Added support for JDBC-4.0's NCLOB, and NCHAR/NVARCHAR types.
+
+10-09-07 - Version 5.0.8
+
+ - Fixed BUG#30550, executeBatch() would fail with an ArithmeticException
+ and/or NullPointerException when the batch had zero members and
+ "rewriteBatchedStatements" was set to "true" for the connection.
+
+ - Added two configuration parameters (both default to "false")
+
+ * blobsAreStrings - Should the driver always treat BLOBs as Strings
+ specifically to work around dubious metadata returned
+ by the server for GROUP BY clauses?
+
+ * functionsNeverReturnBlobs - Should the driver always treat data from
+ functions returning BLOBs as Strings -
+ specifically to work around dubious metadata
+ returned by the server for GROUP BY clauses?
+
+ - Fixed BUG#29106 - Connection checker for JBoss didn't use same method parameters
+ via reflection, causing connections to always seem "bad".
+
+ - Fixed BUG#30664 - Note that this fix only works for MySQL server
+ versions 5.0.25 and newer, since earlier versions didn't consistently
+ return correct metadata for functions, and thus results from
+ subqueries and functions were indistinguishable from each other,
+ leading to type-related bugs.
+
+ - Fixed BUG#28972 - DatabaseMetaData.getTypeInfo() for the types DECIMAL
+ and NUMERIC will return a precision of 254 for server versions older than
+ 5.0.3, 64 for versions 5.0.3-5.0.5 and 65 for versions newer than 5.0.5.
+
+ - Fixed BUG#29852 - Closing a load-balanced connection would cause a
+ ClassCastException.
+
+ - Fixed BUG#27867 - Schema objects with identifiers other than
+ the connection character aren't retrieved correctly in
+ ResultSetMetadata.
+
+ - Fixed BUG#28689 - CallableStatement.executeBatch() doesn't work when
+ connection property "noAccessToProcedureBodies" has been set to "true".
+
+ The fix involves changing the behavior of "noAccessToProcedureBodies",in
+ that the driver will now report all paramters as "IN" paramters
+ but allow callers to call registerOutParameter() on them without throwing
+ an exception.
+
+ - Fixed BUG#27182 - Connection.getServerCharacterEncoding() doesn't work
+ for servers with version >= 4.1.
+
+ - Fixed BUG#27915 - DatabaseMetaData.getColumns() doesn't
+ contain SCOPE_* or IS_AUTOINCREMENT columns.
+
+ - Fixed BUG#30851, NPE with null column values when
+ "padCharsWithSpace" is set to "true".
+
+ - Specifying a "validation query" in your connection pool
+ that starts with "/* ping */" _exactly_ will cause the driver to
+ instead send a ping to the server and return a fake result set (much
+ lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection,
+ will send the ping across all active connections.
+
+ - Fixed Bug#30892 setObject(int, Object, int, int) delegate in
+ PreparedStatmentWrapper delegates to wrong method.
+
+ - XAConnections now start in auto-commit mode (as per JDBC-4.0 specification
+ clarification).
+
+ - Fixed Bug#27412 - cached metadata with PreparedStatement.execute()
+ throws NullPointerException.
+
+ - Driver will now fall back to sane defaults for max_allowed_packet and
+ net_buffer_length if the server reports them incorrectly (and will log
+ this situation at WARN level, since it's actually an error condition).
+
+ - Fixed BUG#27916 - UNSIGNED types not reported via DBMD.getTypeInfo(), and
+ capitalization of type names is not consistent between DBMD.getColumns(),
+ RSMD.getColumnTypeName() and DBMD.getTypeInfo().
+
+ This fix also ensures that the precision of UNSIGNED MEDIUMINT
+ and UNSIGNED BIGINT is reported correctly via DBMD.getColumns().
+
+ - Fixed BUG#31053 - Connections established using URLs of the form
+ "jdbc:mysql:loadbalance://" weren't doing failover if they tried to
+ connect to a MySQL server that was down. The driver now attempts
+ connections to the next "best" (depending on the load balance strategy
+ in use) server, and continues to attempt connecting to the next "best"
+ server every 250 milliseconds until one is found that is up and running
+ or 5 minutes has passed.
+
+ If the driver gives up, it will throw the last-received SQLException.
+
+07-19-07 - Version 5.0.7
+
+ - Setting the configuration parameter "useCursorFetch" to "true" for
+ MySQL-5.0+ enables the use of cursors that allow Connector/J to save
+ memory by fetching result set rows in chunks (where the chunk size
+ is set by calling setFetchSize() on a Statement or ResultSet) by
+ using fully-materialized cursors on the server.
+
+ The driver will will now automatically set "useServerPrepStmts" to
+ "true" when "useCursorFetch" has been set to "true", since the feature
+ requires server-side prepared statements in order to function.
+
+ - Fixed BUG#28469 - PreparedStatement.getMetaData() for statements
+ containing leading one-line comments is not returned correctly.
+
+ As part of this fix, we also overhauled detection of DML for
+ executeQuery() and SELECTs for executeUpdate() in plain and
+ prepared statements to be aware of the same types of comments.
+
+ - Added configuration property "useNanosForElapsedTime" - for
+ profiling/debugging functionality that measures elapsed time,
+ should the driver try to use nanoseconds resolution if available
+ (requires JDK >= 1.5)?
+
+ - Added configuration property "slowQueryThresholdNanos" - if
+ "useNanosForElapsedTime" is set to "true", and this property
+ is set to a non-zero value the driver will use this threshold
+ (in nanosecond units) to determine if a query was slow, instead
+ of using millisecond units.
+
+ Note, that if "useNanosForElapsedTime" is set to "true", and this
+ property is set to "0" (or left default), then elapsed times will
+ still be measured in nanoseconds (if possible), but the slow query
+ threshold will be converted from milliseconds to nanoseconds, and thus
+ have an upper bound of approximately 2000 millesconds (as that threshold
+ is represented as an integer, not a long).
+
+ - Added configuration properties to allow tuning of TCP/IP socket
+ parameters:
+
+ "tcpNoDelay" - Should the driver set SO_TCP_NODELAY (disabling the
+ Nagle Algorithm, default "true")?
+
+ "tcpKeepAlive" - Should the driver set SO_KEEPALIVE (default "true")?
+
+ "tcpRcvBuf" - Should the driver set SO_RCV_BUF to the given value?
+ The default value of '0', means use the platform default
+ value for this property.
+
+ "tcpSndBuf" - Should the driver set SO_SND_BUF to the given value?
+ The default value of '0', means use the platform default
+ value for this property.
+
+ "tcpTrafficClass" - Should the driver set traffic class or
+ type-of-service fields? See the documentation
+ for java.net.Socket.setTrafficClass() for more
+ information.
+
+ - Give more information in EOFExceptions thrown out of MysqlIO (how many
+ bytes the driver expected to read, how many it actually read, say that
+ communications with the server were unexpectedly lost).
+
+ - Setting "useDynamicCharsetInfo" to "false" now causes driver to use
+ static lookups for collations as well (makes
+ ResultSetMetadata.isCaseSensitive() much more efficient, which leads
+ to performance increase for ColdFusion, which calls this method for
+ every column on every table it sees, it appears).
+
+ - Driver detects when it is running in a ColdFusion MX server (tested
+ with version 7), and uses the configuration bundle "coldFusion",
+ which sets useDynamicCharsetInfo to "false" (see previous entry), and
+ sets useLocalSessionState and autoReconnect to "true".
+
+ - Fixed BUG#28851 - parser in client-side prepared statements
+ eats character following '/' if it's not a multi-line comment.
+
+ - Fixed BUG#28956 - parser in client-side prepared statements
+ runs to end of statement, rather than end-of-line for '#' comments.
+
+ Also added support for '--' single-line comments.
+
+ - Don't send any file data in response to LOAD DATA LOCAL INFILE
+ if the feature is disabled at the client side. This is to prevent
+ a malicious server or man-in-the-middle from asking the client for
+ data that the client is not expecting. Thanks to Jan Kneschke for
+ discovering the exploit and Andrey "Poohie" Hristov, Konstantin Osipov
+ and Sergei Golubchik for discussions about implications and possible
+ fixes. This fixes BUG 29605 for JDBC.
+
+ - Added new debugging functionality - Setting configuration property
+ "includeInnodbStatusInDeadlockExceptions" to "true" will cause the driver
+ to append the output of "SHOW ENGINE INNODB STATUS" to deadlock-related
+ exceptions, which will enumerate the current locks held inside InnoDB.
+
+05-15-07 - Version 5.0.6
+
+ - Fixed BUG#25545 - Client options not sent correctly when using SSL,
+ leading to stored procedures not being able to return results. Thanks
+ to Don Cohen for the bug report, testcase and patch.
+
+ - Fixed BUG#26592 - PreparedStatement is not closed in
+ BlobFromLocator.getBytes().
+
+ - Fixed BUG#25624 - Whitespace surrounding storage/size specifiers in
+ stored procedure parameters declaration causes NumberFormatException to
+ be thrown when calling stored procedure on JDK-1.5 or newer, as the Number
+ classes in JDK-1.5+ are whitespace intolerant.
+
+ - Fixed BUG#26173 - When useCursorFetch=true, sometimes server would return
+ new, more exact metadata during the execution of the server-side prepared
+ statement that enables this functionality, which the driver ignored (using
+ the original metadata returned during prepare()), causing corrupt reading
+ of data due to type mismatch when the actual rows were returned.
+
+ - Fixed BUG#26959 - comments in DDL of stored procedures/functions confuse
+ procedure parser, and thus metadata about them can not be created, leading to
+ inability to retrieve said metadata, or execute procedures that have certain
+ comments in them.
+
+ - Give better error message when "streaming" result sets, and the connection
+ gets clobbered because of exceeding net_write_timeout on the server. (which is
+ basically what the error message says too).
+
+ - Fixed BUG#26789 - fast date/time parsing doesn't take into
+ account 00:00:00 as a legal value.
+
+ - Fixed BUG#27317 - ResultSet.get*() with a column index < 1 returns
+ misleading error message.
+
+ - Fixed BUG#25517 - Statement.setMaxRows() is not effective on result
+ sets materialized from cursors.
+
+ - New configuration property, "enableQueryTimeouts" (default "true").
+ When enabled, query timeouts set via Statement.setQueryTimeout() use a
+ shared java.util.Timer instance for scheduling. Even if the timeout
+ doesn't expire before the query is processed, there will be
+ memory used by the TimerTask for the given timeout which won't be
+ reclaimed until the time the timeout would have expired if it
+ hadn't been cancelled by the driver. High-load environments
+ might want to consider disabling this functionality. (this configuration
+ property is part of the "maxPerformance" configuration bundle).
+
+ - Fixed BUG#27400 - CALL /* ... */ some_proc() doesn't work. As a side effect
+ of this fix, you can now use /* */ and # comments when preparing statements using
+ client-side prepared statement emulation.
+
+ If the comments happen to contain parameter markers '?', they will be treated
+ as belonging to the comment (i.e. not recognized) rather than being a parameter
+ of the statement.
+
+ Note that the statement when sent to the server will contain the comments
+ as-is, they're not stripped during the process of preparing the PreparedStatement
+ or CallableStatement.
+
+ - Fixed BUG#25328 - BIT(> 1) is returned as java.lang.String from ResultSet.getObject()
+ rather than byte[].
+
+ - Fixed BUG#25715 - CallableStatements with OUT/INOUT parameters that
+ are "binary" (blobs, bits, (var)binary, java_object) have extra 7 bytes
+ (which happens to be the _binary introducer!)
+
+ - Added configuration property "padCharsWithSpace" (defaults to "false"). If set
+ to "true", and a result set column has the CHAR type and the value does not
+ fill the amount of characters specified in the DDL for the column, the driver
+ will pad the remaining characters with space (for ANSI compliance).
+
+ - Fixed BUG#27655 - Connection.getTransactionIsolation() uses
+ "SHOW VARIABLES LIKE" which is very inefficient on MySQL-5.0+
+
+ - Added configuration property "useDynamicCharsetInfo". If set to "false"
+ (the default), the driver will use a per-connection cache of character set
+ information queried from the server when necessary, or when set to "true",
+ use a built-in static mapping that is more efficient, but isn't aware of
+ custom character sets or character sets implemented after the release of
+ the JDBC driver.
+
+ Note: this only affects the "padCharsWithSpace" configuration property and the
+ ResultSetMetaData.getColumnDisplayWidth() method.
+
+ - More intelligent initial packet sizes for the "shared" packets are used
+ (512 bytes, rather than 16K), and initial packets used during handshake are
+ now sized appropriately as to not require reallocation.
+
+ - Fixed issue where calling getGeneratedKeys() on a prepared statement after
+ calling execute() didn't always return the generated keys (executeUpdate()
+ worked fine however).
+
+ - Fixed issue where a failed-over connection would let an application call
+ setReadOnly(false), when that call should be ignored until the connection
+ is reconnected to a writable master unless "failoverReadOnly" had been set
+ to "false".
+
+ - Fixed BUG#28085 - Generate more useful error messages for diagnostics
+ when the driver thinks a result set isn't updatable. (Thanks to Ashley Martens
+ for the patch).
+
+ - Driver will now use INSERT INTO ... VALUES (DEFAULT) form of statement
+ for updatable result sets for ResultSet.insertRow(), rather than
+ pre-populating the insert row with values from DatabaseMetaData.getColumns()
+ (which results in a "SHOW FULL COLUMNS" on the server for every result
+ set). If an application requires access to the default values before
+ insertRow() has been called, the JDBC URL should be configured with
+ "populateInsertRowWithDefaultValues" set to "true".
+
+ This fix specifically targets performance issues with ColdFusion and the
+ fact that it seems to ask for updatable result sets no matter what the
+ application does with them.
+
+ - com.mysql.jdbc.[NonRegistering]Driver now understands URLs of the format
+ "jdbc:mysql:replication://" and "jdbc:mysql:loadbalance://" which will
+ create a ReplicationConnection (exactly like when
+ using [NonRegistering]ReplicationDriver) and an experimenal load-balanced
+ connection designed for use with SQL nodes in a MySQL Cluster/NDB environment,
+ respectively.
+
+ In an effort to simplify things, we're working on deprecating multiple
+ drivers, and instead specifying different core behavior based upon JDBC URL
+ prefixes, so watch for [NonRegistering]ReplicationDriver to eventually
+ disappear, to be replaced with com.mysql.jdbc[NonRegistering]Driver with
+ the new URL prefix.
+
+ - Added an experimental load-balanced connection designed for use with SQL nodes
+ in a MySQL Cluster/NDB environment (This is not for master-slave replication.
+ For that, we suggest you look at ReplicationConnection or "lbpool").
+
+ If the JDBC URL starts with "jdbc:mysql:loadbalance://host-1,host-2,...host-n",
+ the driver will create an implementation of java.sql.Connection that load
+ balances requests across a series of MySQL JDBC connections to the given hosts,
+ where the balancing takes place after transaction commit.
+
+ Therefore, for this to work (at all), you must use transactions, even if only
+ reading data.
+
+ Physical connections to the given hosts will not be created until needed.
+
+ The driver will invalidate connections that it detects have had
+ communication errors when processing a request. A new connection to the
+ problematic host will be attempted the next time it is selected by the load
+ balancing algorithm.
+
+ There are two choices for load balancing algorithms, which may be specified
+ by the "loadBalanceStrategy" JDBC URL configuration property:
+
+ * "random" - the driver will pick a random host for each request. This tends
+ to work better than round-robin, as the randomness will somewhat account for
+ spreading loads where requests vary in response time, while round-robin
+ can sometimes lead to overloaded nodes if there are variations in response times
+ across the workload.
+
+ * "bestResponseTime" - the driver will route the request to the host that had
+ the best response time for the previous transaction.
+
+ - When "useLocalSessionState" is set to "true" and connected to a MySQL-5.0 or
+ later server, the JDBC driver will now determine whether an actual "commit" or
+ "rollback" statement needs to be sent to the database when Connection.commit()
+ or Connection.rollback() is called.
+
+ This is especially helpful for high-load situations with connection pools that
+ always call Connection.rollback() on connection check-in/check-out because it
+ avoids a round-trip to the server.
+
+03-01-07 - Version 5.0.5
+
+ - Fixed BUG#23645 - Some collations/character sets reported as "unknown"
+ (specifically cias variants of existing character sets), and inability to override
+ the detected server character set.
+
+ - Performance enhancement of initial character set configuration, driver
+ will only send commands required to configure connection character set
+ session variables if the current values on the server do not match
+ what is required.
+
+ - Fixed BUG#24360 .setFetchSize() breaks prepared SHOW and other commands.
+
+ - Fixed BUG#24344 - useJDBCCompliantTimezoneShift with server-side prepared
+ statements gives different behavior than when using client-side prepared
+ statements. (this is now fixed if moving from server-side prepared statements
+ to client-side prepared statements by setting "useSSPSCompatibleTimezoneShift" to
+ true", as the driver can't tell if this is a new deployment that never used
+ server-side prepared statements, or if it is an existing deployment that is
+ switching to client-side prepared statements from server-side prepared statements.
+
+ - Fixed BUG#23304 - DBMD using "show" and DBMD using information_schema do
+ not return results consistent with each other. (note this fix only
+ addresses the inconsistencies, not the issue that the driver is
+ treating schemas differently than some users expect. We will revisit
+ this behavior when there is full support for schemas in MySQL).
+
+ - Fixed BUG#25073 - rewriting batched statements leaks internal statement
+ instances, and causes a memory leak.
+
+ - Fixed issue where field-level for metadata from DatabaseMetaData when using
+ INFORMATION_SCHEMA didn't have references to current connections,
+ sometimes leading to NullPointerExceptions when intropsecting them via
+ ResultSetMetaData.
+
+ - Fixed BUG#25025 - Client-side prepared statement parser gets confused by
+ in-line (/* ... */) comments and therefore can't rewrite batched statements
+ or reliably detect type of statements when they're used.
+
+ - Fixed BUG#24065 - Better error message when server doesn't return enough
+ information to determine stored procedure/function parameter types.
+
+ - Fixed BUG#21438 - Driver sending nanoseconds to server for timestamps when
+ using server-side prepared statements, when server expects microseconds.
+
+ - Fixed BUG#25514 - Timer instance used for Statement.setQueryTimeout()
+ created per-connection, rather than per-VM, causing memory leak
+
+ - Fixed BUG#25009 - Results from updates not handled correctly in
+ multi-statement queries, leading to erroneous "Result is from UPDATE"
+ exceptions.
+
+ - Fixed BUG#25047 - StringUtils.indexOfIgnoreCaseRespectQuotes() isn't
+ case-insensitive on the first character of the target. This bug broke
+ rewriteBatchedStatements functionality when prepared statements don't
+ use upper-case for the VALUES clause in their statements.
+
+ - Fixed BUG#21480 - Some exceptions thrown out of StandardSocketFactory
+ were needlessly wrapped, obscurring their true cause, especially when
+ using socket timeouts.
+
+ - Fixed BUG#23303 - DatabaseMetaData.getSchemas() doesn't return a
+ TABLE_CATALOG column.
+
+ - Fixed BUG#25399 - EscapeProcessor gets confused by multiple
+ backslashes. We now push the responsibility of syntax errors back
+ on to the server for most escape sequences.
+
+ - Fixed BUG#25379 - INOUT parameters in CallableStatements get
+ doubly-escaped.
+
+ - Removed non-short-circuited logical ORs from "if" statements.
+
+ - Re-worked stored procedure parameter parser to be more robust. Driver no
+ longer requires "BEGIN" in stored procedure definition, but does have
+ requirement that if a stored function begins with a label directly after the
+ "returns" clause, that the label is not a quoted identifier.
+ - Reverted back to internal character conversion routines for single-byte
+ character sets, as the ones internal to the JVM are using much more CPU
+ time than our internal implementation.
+
+ - Changed cached result set metadata (when using
+ "cacheResultSetMetadata=true") to be cached per-connection rather
+ than per-statement as previously implemented.
+
+ - Use a java.util.TreeMap to map column names to ordinal indexes for
+ ResultSet.findColumn() instead of a HashMap. This allows us to have
+ case-insensitive lookups (required by the JDBC specification) without
+ resorting to the many transient object instances needed to support this
+ requirement with a normal HashMap with either case-adjusted keys, or
+ case-insensitive keys. (In the worst case scenario for lookups of a 1000
+ column result set, TreeMaps are about half as fast wall-clock time as
+ a HashMap, however in normal applications their use gives many orders
+ of magnitude reduction in transient object instance creation which pays
+ off later for CPU usage in garbage collection).
+
+ - Avoid static synchronized code in JVM class libraries for dealing with
+ default timezones.
+
+ - Fixed cases where ServerPreparedStatements weren't using cached metadata
+ when "cacheResultSetMetadata=true" was configured.
+
+ - Use faster datetime parsing for ResultSets that come from plain or
+ non-server-side prepared statements. (Enable old implementation with
+ "useFastDateParsing=false" as a configuration parameter).
+
+ - Fixed BUG#24794 - DatabaseMetaData.getSQLKeywords() doesn't return
+ all reserved words for current MySQL version. The current fix/implementation
+ returns keywords for MySQL-5.1, and doesn't distinguish between different
+ versions of the server.
+
+ - When using cached metadata, skip field-level metadata packets coming from
+ the server, rather than reading them and discarding them without creating
+ com.mysql.jdbc.Field instances.
+
+ - Fixed BUG#25836 - Statement execution which timed out doesn't always
+ throw MySQLTimeoutException.
+
+ - Throw exceptions encountered during timeout to thread
+ calling Statement.execute*(), rather than RuntimeException.
+
+ - Added configuration property "localSocketAddress",which is the hostname or
+ IP address given to explicitly configure the interface that the driver will
+ bind the client side of the TCP/IP connection to when connecting.
+
+ - Take "localSocketAddress" property into account when creating instances
+ of CommunicationsException when the underyling exception is a
+ java.net.BindException, so that a friendlier error message is given with
+ a little internal diagnostics.
+
+ - Fixed some NPEs when cached metadata was used with UpdatableResultSets.
+
+ - The "rewriteBatchedStatements" feature can now be used with server-side
+ prepared statements.
+
+ - Fixed BUG#26326 - Connection property "socketFactory" wasn't exposed via
+ correctly named mutator/accessor, causing data source implementations that
+ use JavaBean naming conventions to set properties to fail to set the property
+ (and in the case of SJAS, fail silently when trying to set this parameter).
+
+ - Fixed BUG#25787 - java.util.Date should be serialized for
+ PreparedStatement.setObject().
+
+ We've added a new configuration option "treatUtilDateAsTimestamp", which is
+ false by default, as (1) We already had specific behavior to treat
+ java.util.Date as a java.sql.Timestamp because it's useful to many folks,
+ and (2) that behavior will very likely be required for drivers JDBC-post-4.0.
+
+ - Fixed BUG#22628 - Driver.getPropertyInfo() throws NullPointerException for
+ URL that only specifies host and/or port.
+
+ - Fixed BUG#21267, ParameterMetaData throws NullPointerException when
+ prepared SQL actually has a syntax error. Added
+ "generateSimpleParameterMetadata" configuration property, which when set
+ to "true" will generate metadata reflecting VARCHAR for every parameter
+ (the default is "false", which will cause an exception to be thrown if no
+ parameter metadata for the statement is actually available).
+
+ - When extracting foreign key information from "SHOW CREATE TABLE " in
+ DatabaseMetaData, ignore exceptions relating to tables being missing
+ (which could happen for cross-reference or imported-key requests, as
+ the list of tables is generated first, then iterated).
+
+ - Fixed logging of XA commands sent to server, it's now configurable
+ via "logXaCommands" property (defaults to "false").
+
+ - Fixed issue where XADataSources couldn't be bound into JNDI,
+ as the DataSourceFactory didn't know how to create instances
+ of them.
+
+ - Fixed issue where XADataSources couldn't be bound into JNDI,
+ as the DataSourceFactory didn't know how to create instances
+ of them.
+
+ - Usage advisor will now issue warnings for result sets with large numbers
+ of rows (size configured by "resultSetSizeThreshold" property, default
+ value is 100).
+
+10-20-06 - Version 5.0.4
+
+ - Fixed BUG#21379 - column names don't match metadata in cases
+ where server doesn't return original column names (column functions)
+ thus breaking compatibility with applications that expect 1-1 mappings
+ between findColumn() and rsmd.getColumnName(), usually manifests itself
+ as "Can't find column ('')" exceptions.
+
+ - Fixed BUG#21544 - When using information_schema for metadata,
+ COLUMN_SIZE for getColumns() is not clamped to range of
+ java.lang.Integer as is the case when not using
+ information_schema, thus leading to a truncation exception that
+ isn't present when not using information_schema.
+
+ - Fixed configuration property "jdbcCompliantTruncation" was not
+ being used for reads of result set values.
+
+ - Fixed BUG#22024 - Newlines causing whitespace to span confuse
+ procedure parser when getting parameter metadata for stored
+ procedures.
+
+ - Driver now supports {call sp} (without "()" if procedure has no
+ arguments).
+
+ - Fixed BUG#22359 - Driver was using milliseconds for
+ Statement.setQueryTimeout() when specification says argument is
+ to be in seconds.
+
+ - Workaround for server crash when calling stored procedures
+ via a server-side prepared statement (driver now detects
+ prepare(stored procedure) and substitutes client-side prepared
+ statement), addresses BUG#22297.
+
+ - Added new _ci collations to CharsetMapping, fixing
+ Bug#22456 - utf8_unicode_ci not working.
+
+ - Fixed BUG#22290 - Driver issues truncation on write exception when
+ it shouldn't (due to sending big decimal incorrectly to server with
+ server-side prepared statement).
+
+ - Fixed BUG#22613 - DBMD.getColumns() does not return expected
+ COLUMN_SIZE for the SET type, now returns length of largest possible
+ set disregarding whitespace or the "," delimitters to be consistent
+ with the ODBC driver.
+
+ - Driver now sends numeric 1 or 0 for client-prepared statement
+ setBoolean() calls instead of '1' or '0'.
+
+ - DatabaseMetaData correctly reports true for supportsCatalog*()
+ methods.
+
+07-26-06 - Version 5.0.3
+
+ - Fixed BUG#20650 - Statement.cancel() causes NullPointerException
+ if underlying connection has been closed due to server failure.
+
+ - Added configuration option "noAccessToProcedureBodies" which will
+ cause the driver to create basic parameter metadata for
+ CallableStatements when the user does not have access to procedure
+ bodies via "SHOW CREATE PROCEDURE" or selecting from mysql.proc
+ instead of throwing an exception. The default value for this option
+ is "false".
+
+07-11-06 - Version 5.0.2-beta (5.0.1 not released due to packaging error)
+
+ - Fixed BUG#17401 - Can't use XAConnection for local transactions when
+ no global transaction is in progress.
+
+ - Fixed BUG#18086 - Driver fails on non-ASCII platforms. The driver
+ was assuming that the platform character set would be a superset
+ of MySQL's "latin1" when doing the handshake for authentication,
+ and when reading error messages. We now use Cp1252 for all strings
+ sent to the server during the handshake phase, and a hard-coded mapping
+ of the "language" server variable to the character set that
+ is used for error messages.
+
+ - Fixed BUG#19169 - ConnectionProperties (and thus some
+ subclasses) are not serializable, even though some J2EE containers
+ expect them to be.
+
+ - Fixed BUG#20242 - MysqlValidConnectionChecker for JBoss doesn't
+ work with MySQLXADataSources.
+
+ - Better caching of character set converters (per-connection)
+ to remove a bottleneck for multibyte character sets.
+
+ - Added connection/datasource property "pinGlobalTxToPhysicalConnection"
+ (defaults to "false"). When set to "true", when using XAConnections, the
+ driver ensures that operations on a given XID are always routed to the
+ same physical connection. This allows the XAConnection to support
+ "XA START ... JOIN" after "XA END" has been called, and is also a
+ workaround for transaction managers that don't maintain thread affinity
+ for a global transaction (most either always maintain thread affinity,
+ or have it as a configuration option).
+
+ - MysqlXaConnection.recover(int flags) now allows combinations of
+ XAResource.TMSTARTRSCAN and TMENDRSCAN. To simulate the "scanning"
+ nature of the interface, we return all prepared XIDs for TMSTARTRSCAN,
+ and no new XIDs for calls with TMNOFLAGS, or TMENDRSCAN when not in
+ combination with TMSTARTRSCAN. This change was made for API compliance,
+ as well as integration with IBM WebSphere's transaction manager.
+
+12-23-05 - Version 5.0.0-beta
+
+ - XADataSource implemented (ported from 3.2 branch which won't be
+ released as a product). Use
+ "com.mysql.jdbc.jdbc2.optional.MysqlXADataSource" as your datasource
+ class name in your application server to utilize XA transactions
+ in MySQL-5.0.10 and newer.
+
+ - PreparedStatement.setString() didn't work correctly when
+ sql_mode on server contained NO_BACKSLASH_ESCAPES, and no characters
+ that needed escaping were present in the string.
+
+ - Attempt detection of the MySQL type "BINARY" (it's an alias, so this isn't
+ always reliable), and use the java.sql.Types.BINARY type mapping for it.
+
+ - Moved -bin-g.jar file into separate "debug" subdirectory to avoid confusion.
+
+ - Don't allow .setAutoCommit(true), or .commit() or .rollback() on an XA-managed
+ connection as-per the JDBC specification.
+
+ - If the connection "useTimezone" is set to "true", then also respect timezone
+ conversions in escape-processed string literals (e.g. "{ts ...}" and
+ "{t ...}").
+
+ - Return original column name for RSMD.getColumnName() if the column was aliased,
+ alias name for .getColumnLabel() (if aliased), and original table name
+ for .getTableName(). Note this only works for MySQL-4.1 and newer, as
+ older servers don't make this information available to clients.
+
+ - Setting "useJDBCCompliantTimezoneShift=true" (it's not the default)
+ causes the driver to use GMT for _all_ TIMESTAMP/DATETIME timezones,
+ and the current VM timezone for any other type that refers to timezones.
+ This feature can not be used when "useTimezone=true" to convert between
+ server and client timezones.
+
+ - Add one level of indirection of internal representation of CallableStatement
+ parameter metadata to avoid class not found issues on JDK-1.3 for
+ ParameterMetadata interface (which doesn't exist prior to JDBC-3.0).
+
+ - Added unit tests for XADatasource, as well as friendlier exceptions
+ for XA failures compared to the "stock" XAException (which has no
+ messages).
+
+ - Fixed BUG#14279 - Idle timeouts cause XAConnections to whine about rolling
+ themselves back
+
+ - Added support for Connector/MXJ integration via url subprotocol
+ "jdbc:mysql:mxj://....".
+
+ - Moved all SQLException constructor usage to a factory in SQLError
+ (ground-work for JDBC-4.0 SQLState-based exception classes).
+
+ - Removed Java5-specific calls to BigDecimal constructor (when
+ result set value is '', (int)0 was being used as an argument
+ in-directly via method return value. This signature doesn't exist
+ prior to Java5.)
+
+ - Moved all SQLException creation to a factory method in SQLError,
+ groundwork for JDBC-4.0 SQLState class-based exceptions.
+
+ - Added service-provider entry to META-INF/services/java.sql.Driver
+ for JDBC-4.0 support.
+
+ - Return "[VAR]BINARY" for RSMD.getColumnTypeName() when that is actually
+ the type, and it can be distinguished (MySQL-4.1 and newer).
+
+ - When fix for BUG#14562 was merged from 3.1.12, added functionality
+ for CallableStatement's parameter metadata to return correct
+ information for .getParameterClassName().
+
+ - Fuller synchronization of Connection to avoid deadlocks when
+ using multithreaded frameworks that multithread a single connection
+ (usually not recommended, but the JDBC spec allows it anyways),
+ part of fix to BUG#14972).
+
+ - Implementation of Statement.cancel() and Statement.setQueryTimeout().
+ Both require MySQL-5.0.0 or newer server, require a separate connection
+ to issue the "KILL QUERY" command, and in the case of setQueryTimeout()
+ creates an additional thread to handle the timeout functionality.
+
+ Note: Failures to cancel the statement for setQueryTimeout() may manifest
+ themselves as RuntimeExceptions rather than failing silently, as there
+ is currently no way to unblock the thread that is executing the query being
+ cancelled due to timeout expiration and have it throw the exception
+ instead.
+
+ - Removed dead code in com.mysql.jdbc.Connection.
+
+ - Made construction of com.mysql.jdbc.Field (result set metadata)
+ instances more efficient for non-string types by not doing
+ character set initialization, or detection of type changes due to
+ temporary tables.
+
+ - Removed redundant code in com.mysql.jdbc.MysqlIO.
+
+ - Removed work done for BUG#14652, and instead loosened synchronization
+ to solve a number of deadlock issues in BUG#18719, BUG#18367, BUG#17709
+ and BUG#15067. New strategy basically makes Connection instances threadsafe
+ and thus shareable across threads, and anything else threadsafe, but not
+ necessarily shareable across threads due to JDBC API interactions that
+ can cause non-obvious behavior and/or deadlock scenarios to occur since
+ the API is not designed to be used from multiple threads at once.
+
+ Therefore, unless external synchronization is provided, clients should
+ not allow multiple threads to share a given statement or result set. Examples
+ of issues with the API itself not being multi-thread suitable include,
+ but are not limited to race conditions between modifiers and execution and
+ retrieval methods on statements and result sets that are not synchronizable
+ such as ResultSet.get*() and traversal methods, or Statement.execute*() closing
+ result sets without effectively making the driver itself serializable across the
+ board.
+
+ These changes should not have any effect on "normal" J(2)EE use cases
+ where only one thread ever uses a connection instance and the objects created by
+ it.
+
+ - Use a java.util.Timer to schedule cancellation of queries via
+ Statement.setQueryTimeout() rather than one thread per potential cancellation.
+
+ A new thread will be used to actually cancel a running query, as there's potential
+ for a cancel request to block other cancel requests if all run from the
+ same thread.
+
+nn-nn-07 - Version 3.1.15
+
+ - Fixed BUG#23281 - Downed slave caused round-robin load balance to
+ not cycle back to first host in list.
+
+ - Disabled use of server-side prepared statements by default.
+
+ - Handle YYYY-MM-DD hh:mm:ss format of timestamp in
+ ResultSet.getTimeFromString().
+
+ - Fixed BUG#24840 - character encoding of "US-ASCII" doesn't map correctly
+ for 4.1 or newer
+
+ - Added Implementation-Vendor-Id attribute to jar manifest per request
+ in BUG#15641.
+
+ - C3P0 >= version 0.9.1 passes non-proxied connections to
+ MysqlConnectionTester, thus it began throwing ClassCastExceptions.
+ MysqlConnectionTester now checks if it has a plain Connection and uses
+ that if possible. Thanks to Brian Skrab for the fix.
+
+10-19-06 - Version 3.1.14
+
+ - Fixed BUG#20479 - Updatable result set throws ClassCastException
+ when there is row data and moveToInsertRow() is called.
+
+ - Fixed BUG#20485 - Updatable result set that contains
+ a BIT column fails when server-side prepared statements are used.
+
+ - Fixed BUG#16987 - Memory leak with profileSQL=true.
+
+ - Fixed BUG#19726 - Connection fails to localhost when using
+ timeout and IPv6 is configured.
+
+ - Fixed BUG#16791 - NullPointerException in MysqlDataSourceFactory
+ due to Reference containing RefAddrs with null content.
+
+ - Fixed BUG#20306 - ResultSet.getShort() for UNSIGNED TINYINT
+ returns incorrect values when using server-side prepared statements.
+
+ - Fixed BUG#20687 - Can't pool server-side prepared statements, exception
+ raised when re-using them.
+
+ - Fixed BUG#21062 - ResultSet.getSomeInteger() doesn't work for BIT(>1).
+
+ - Fixed BUG#18880 - ResultSet.getFloatFromString() can't retrieve
+ values near Float.MIN/MAX_VALUE.
+
+ - Fixed BUG#20888 - escape of quotes in client-side prepared
+ statements parsing not respected. Patch covers more than bug report,
+ including NO_BACKSLASH_ESCAPES being set, and stacked quote characters
+ forms of escaping (i.e. '' or "").
+
+ - Fixed BUG#19993 - ReplicationDriver does not always round-robin load
+ balance depending on URL used for slaves list.
+
+ - Fixed calling toString() on ResultSetMetaData for driver-generated
+ (i.e. from DatabaseMetaData method calls, or from getGeneratedKeys())
+ result sets would raise a NullPointerException.
+
+ - Fixed Bug#21207 - Driver throws NPE when tracing prepared statements that
+ have been closed (in asSQL()).
+
+ - Removed logger autodectection altogether, must now specify logger
+ explitly if you want to use a logger other than one that logs
+ to STDERR.
+
+ - Fixed BUG#22290 - Driver issues truncation on write exception when
+ it shouldn't (due to sending big decimal incorrectly to server with
+ server-side prepared statement).
+
+ - Driver now sends numeric 1 or 0 for client-prepared statement
+ setBoolean() calls instead of '1' or '0'.
+
+ - Fixed bug where driver would not advance to next host if
+ roundRobinLoadBalance=true and the last host in the list is down.
+
+ - Fixed BUG#18258 - DatabaseMetaData.getTables(), columns() with bad
+ catalog parameter threw exception rather than return empty result
+ set (as required by spec).
+
+ - Check and store value for continueBatchOnError property in constructor
+ of Statements, rather than when executing batches, so that Connections
+ closed out from underneath statements don't cause NullPointerExceptions
+ when it's required to check this property.
+
+ - Fixed bug when calling stored functions, where parameters weren't
+ numbered correctly (first parameter is now the return value, subsequent
+ parameters if specified start at index "2").
+
+ - Fixed BUG#21814 - time values outside valid range silently wrap.
+
+05-26-06 - Version 3.1.13
+
+ - Fixed BUG#15464 - INOUT parameter does not store IN value.
+
+ - Fixed BUG#14609 - Exception thrown for new decimal type when
+ using updatable result sets.
+
+ - Fixed BUG#15544, no "dos" character set in MySQL > 4.1.0
+
+ - Fixed BUG#15383 - PreparedStatement.setObject() serializes
+ BigInteger as object, rather than sending as numeric value
+ (and is thus not complementary to .getObject() on an UNSIGNED
+ LONG type).
+
+ - Fixed BUG#11874 - ResultSet.getShort() for UNSIGNED TINYINT
+ returned wrong values.
+
+ - Fixed BUG#15676 - lib-nodist directory missing from
+ package breaks out-of-box build
+
+ - Fixed BUG#15854 - DBMD.getColumns() returns wrong type for BIT.
+
+ - Fixed BUG#16169 - ResultSet.getNativeShort() causes stack overflow error
+ via recurisve calls.
+
+ - Fixed BUG#14938 - Unable to initialize character set mapping tables.
+ Removed reliance on .properties files to hold this information, as it
+ turns out to be too problematic to code around class loader hierarchies
+ that change depending on how an application is deployed. Moved information
+ back into the CharsetMapping class.
+
+ - Fixed BUG#16841 - updatable result set doesn't return AUTO_INCREMENT
+ values for insertRow() when multiple column primary keys are used. (the
+ driver was checking for the existence of single-column primary keys and
+ an autoincrement value > 0 instead of a straightforward isAutoIncrement()
+ check).
+
+ - Fixed BUG#17099 - Statement.getGeneratedKeys() throws NullPointerException
+ when no query has been processed.
+
+ - Fixed BUG#13469 - Driver tries to call methods that don't exist on older and
+ newer versions of Log4j. The fix is not trying to auto-detect presense of log4j,
+ too many different incompatible versions out there in the wild to do this reliably.
+
+ If you relied on autodetection before, you will need to add
+ "logger=com.mysql.jdbc.log.Log4JLogger" to your JDBC URL to enable Log4J usage,
+ or alternatively use the new "CommonsLogger" class to take care of this.
+
+ - Added support for Apache Commons logging, use "com.mysql.jdbc.log.CommonsLogger"
+ as the value for the "logger" configuration property.
+
+ - LogFactory now prepends "com.mysql.jdbc.log" to log class name if it can't be
+ found as-specified. This allows you to use "short names" for the built-in log
+ factories, for example "logger=CommonsLogger" instead of
+ "logger=com.mysql.jdbc.log.CommonsLogger".
+
+ - Fixed BUG#15570 - ReplicationConnection incorrectly copies state,
+ doesn't transfer connection context correctly when transitioning between
+ the same read-only states.
+
+ - Fixed BUG#18041 - Server-side prepared statements don't cause
+ truncation exceptions to be thrown when truncation happens.
+
+ - Added performance feature, re-writing of batched executes for
+ Statement.executeBatch() (for all DML statements) and
+ PreparedStatement.executeBatch() (for INSERTs with VALUE clauses
+ only). Enable by using "rewriteBatchedStatements=true" in your JDBC URL.
+
+ - Fixed BUG#17898 - registerOutParameter not working when some
+ parameters pre-populated. Still waiting for feedback from JDBC experts
+ group to determine what correct parameter count from getMetaData()
+ should be, however.
+
+ - Fixed BUG#17587 - clearParameters() on a closed prepared statement
+ causes NPE.
+
+ - Map "latin1" on MySQL server to CP1252 for MySQL > 4.1.0.
+
+ - Added additional accessor and mutator methods on ConnectionProperties
+ so that DataSource users can use same naming as regular URL properties.
+
+ - Fixed BUG#18740 - Data truncation and getWarnings() only returns last
+ warning in set.
+
+ - Improved performance of retrieving BigDecimal, Time, Timestamp and Date
+ values from server-side prepared statements by creating fewer short-lived
+ instances of Strings when the native type is not an exact match for
+ the requested type. Fixes BUG#18496 for BigDecimals.
+
+ - Fixed BUG#18554 - Aliased column names where length of name > 251
+ are corrupted.
+
+ - Fixed BUG#17450 - ResultSet.wasNull() not always reset
+ correctly for booleans when done via conversion for server-side
+ prepared statements.
+
+ - Fixed BUG#16277 - Invalid classname returned for
+ RSMD.getColumnClassName() for BIGINT type.
+
+ - Fixed case where driver wasn't reading server status correctly when
+ fetching server-side prepared statement rows, which in some cases
+ could cause warning counts to be off, or multiple result sets to not
+ be read off the wire.
+
+ - Driver now aware of fix for BIT type metadata that went into
+ MySQL-5.0.21 for server not reporting length consistently (bug
+ number 13601).
+
+ - Fixed BUG#19282 - ResultSet.wasNull() returns incorrect value
+ when extracting native string from server-side prepared statement
+ generated result set.
+
+11-30-05 - Version 3.1.12
+
+ - Fixed client-side prepared statement bug with embedded ? inside
+ quoted identifiers (it was recognized as a placeholder, when it
+ was not).
+
+ - Don't allow executeBatch() for CallableStatements with registered
+ OUT/INOUT parameters (JDBC compliance).
+
+ - Fall back to platform-encoding for URLDecoder.decode() when
+ parsing driver URL properties if the platform doesn't have a
+ two-argument version of this method.
+
+ - Fixed BUG#14562 - Java type conversion may be incorrect for
+ mediumint.
+
+ - Added configuration property "useGmtMillisForDatetimes" which
+ when set to true causes ResultSet.getDate(), .getTimestamp() to
+ return correct millis-since GMT when .getTime() is called on
+ the return value (currently default is "false" for legacy
+ behavior).
+
+ - Fixed DatabaseMetaData.stores*Identifiers():
+
+ * if lower_case_table_names=0 (on server):
+
+ storesLowerCaseIdentifiers() returns false
+ storesLowerCaseQuotedIdentifiers() returns false
+ storesMixedCaseIdentifiers() returns true
+ storesMixedCaseQuotedIdentifiers() returns true
+ storesUpperCaseIdentifiers() returns false
+ storesUpperCaseQuotedIdentifiers() returns true
+
+ * if lower_case_table_names=1 (on server):
+
+ storesLowerCaseIdentifiers() returns true
+ storesLowerCaseQuotedIdentifiers() returns true
+ storesMixedCaseIdentifiers() returns false
+ storesMixedCaseQuotedIdentifiers() returns false
+ storesUpperCaseIdentifiers() returns false
+ storesUpperCaseQuotedIdentifiers() returns true
+
+ - Fixed BUG#14815 - DatabaseMetaData.getColumns() doesn't
+ return TABLE_NAME correctly.
+
+ - Fixed BUG#14909 - escape processor replaces quote character
+ in quoted string with string delimiter.
+
+ - Fixed BUG#12975 - OpenOffice expects
+ DBMD.supportsIntegrityEnhancementFacility() to return "true"
+ if foreign keys are supported by the datasource, even though
+ this method also covers support for check constraints,
+ which MySQL _doesn't_ have. Setting the configuration property
+ "overrideSupportsIntegrityEnhancementFacility" to "true" causes
+ the driver to return "true" for this method.
+
+ - Added "com.mysql.jdbc.testsuite.url.default" system property to
+ set default JDBC url for testsuite (to speed up bug resolution
+ when I'm working in Eclipse).
+
+ - Fixed BUG#14938 - Unable to initialize character set mapping
+ tables (due to J2EE classloader differences).
+
+ - Fixed BUG#14972 - Deadlock while closing server-side prepared
+ statements from multiple threads sharing one connection.
+
+ - Fixed BUG#12230 - logSlowQueries should give better info.
+
+ - Fixed BUG#13775 - Extraneous sleep on autoReconnect.
+
+ - Fixed BUG#15024 - Driver incorrectly closes streams passed as
+ arguments to PreparedStatements. Reverts to legacy behavior by
+ setting the JDBC configuration property "autoClosePStmtStreams"
+ to "true" (also included in the 3-0-Compat configuration "bundle").
+
+ - Fixed BUG#13048 - maxQuerySizeToLog is not respected. Added logging of
+ bound values for execute() phase of server-side prepared statements
+ when profileSQL=true as well.
+
+ - Fixed BUG#15065 - Usage advisor complains about unreferenced
+ columns, even though they've been referenced.
+
+ - Don't increase timeout for failover/reconnect (BUG#6577)
+
+ - Process escape tokens in Connection.prepareStatement(...), fix
+ for BUG#15141. You can disable this behavior by setting
+ the JDBC URL configuration property "processEscapeCodesForPrepStmts"
+ to "false".
+
+ - Fixed BUG#13255 - Reconnect during middle of executeBatch()
+ should not occur if autoReconnect is enabled.
+
+10-07-05 - Version 3.1.11
+
+ - Fixed BUG#11629 - Spurious "!" on console when character
+ encoding is "utf8".
+
+ - Fixed statements generated for testcases missing ";" for
+ "plain" statements.
+
+ - Fixed BUG#11663 - Incorrect generation of testcase scripts
+ for server-side prepared statements.
+
+ - Fixed regression caused by fix for BUG#11552 that caused driver
+ to return incorrect values for unsigned integers when those
+ integers where within the range of the positive signed type.
+
+ - Moved source code to svn repo.
+
+ - Fixed BUG#11797 - Escape tokenizer doesn't respect stacked single quotes
+ for escapes.
+
+ - GEOMETRY type not recognized when using server-side prepared statements.
+
+ - Fixed BUG#11879 -- ReplicationConnection won't switch to slave, throws
+ "Catalog can't be null" exception.
+
+ - Fixed BUG#12218, properties shared between master and slave with
+ replication connection.
+
+ - Fixed BUG#10630, Statement.getWarnings() fails with NPE if statement
+ has been closed.
+
+ - Only get char[] from SQL in PreparedStatement.ParseInfo() when needed.
+
+ - Fixed BUG#12104 - Geometry types not handled with server-side prepared
+ statements.
+
+ - Fixed BUG#11614 - StringUtils.getBytes() doesn't work when using
+ multibyte character encodings and a length in _characters_ is
+ specified.
+
+ - Fixed BUG#11798 - Pstmt.setObject(...., Types.BOOLEAN) throws exception.
+
+ - Fixed BUG#11976 - maxPerformance.properties mis-spells
+ "elideSetAutoCommits".
+
+ - Fixed BUG#11575 -- DBMD.storesLower/Mixed/UpperIdentifiers()
+ reports incorrect values for servers deployed on Windows.
+
+ - Fixed BUG#11190 - ResultSet.moveToCurrentRow() fails to work when
+ preceeded by a call to ResultSet.moveToInsertRow().
+
+ - Fixed BUG#11115, VARBINARY data corrupted when using server-side
+ prepared statements and .setBytes().
+
+ - Fixed BUG#12229 - explainSlowQueries hangs with server-side
+ prepared statements.
+
+ - Fixed BUG#11498 - Escape processor didn't honor strings demarcated
+ with double quotes.
+
+ - Lifted restriction of changing streaming parameters with server-side
+ prepared statements. As long as _all_ streaming parameters were set
+ before execution, .clearParameters() does not have to be called.
+ (due to limitation of client/server protocol, prepared statements
+ can not reset _individual_ stream data on the server side).
+
+ - Reworked Field class, *Buffer, and MysqlIO to be aware of field
+ lengths > Integer.MAX_VALUE.
+
+ - Updated DBMD.supportsCorrelatedQueries() to return true for versions >
+ 4.1, supportsGroupByUnrelated() to return true and
+ getResultSetHoldability() to return HOLD_CURSORS_OVER_COMMIT.
+
+ - Fixed BUG#12541 - Handling of catalog argument in
+ DatabaseMetaData.getIndexInfo(), which also means changes to the following
+ methods in DatabaseMetaData:
+
+ - getBestRowIdentifier()
+ - getColumns()
+ - getCrossReference()
+ - getExportedKeys()
+ - getImportedKeys()
+ - getIndexInfo()
+ - getPrimaryKeys()
+ - getProcedures() (and thus indirectly getProcedureColumns())
+ - getTables()
+
+ The "catalog" argument in all of these methods now behaves in the following
+ way:
+
+ - Specifying NULL means that catalog will not be used to filter the
+ results (thus all databases will be searched), unless you've
+ set "nullCatalogMeansCurrent=true" in your JDBC URL properties.
+
+ - Specifying "" means "current" catalog, even though this isn't quite
+ JDBC spec compliant, it's there for legacy users.
+
+ - Specifying a catalog works as stated in the API docs.
+
+ - Made Connection.clientPrepare() available from "wrapped" connections
+ in the jdbc2.optional package (connections built by
+ ConnectionPoolDataSource instances).
+
+ - Added Connection.isMasterConnection() for clients to be able to determine
+ if a multi-host master/slave connection is connected to the first host
+ in the list.
+
+ - Fixed BUG#12753 - Tokenizer for "=" in URL properties was causing
+ sessionVariables=.... to be parameterized incorrectly.
+
+ - Fixed BUG#11781, foreign key information that is quoted is
+ parsed incorrectly when DatabaseMetaData methods use that
+ information.
+
+ - The "sendBlobChunkSize" property is now clamped to "max_allowed_packet"
+ with consideration of stream buffer size and packet headers to avoid
+ PacketTooBigExceptions when "max_allowed_packet" is similar in size
+ to the default "sendBlobChunkSize" which is 1M.
+
+ - CallableStatement.clearParameters() now clears resources associated
+ with INOUT/OUTPUT parameters as well as INPUT parameters.
+
+ - Fixed BUG#12417 - Connection.prepareCall() is database name
+ case-sensitive (on Windows systems).
+
+ - Fixed BUG#12752 - Cp1251 incorrectly mapped to win1251 for
+ servers newer than 4.0.x.
+
+ - Fixed BUG#12970 - java.sql.Types.OTHER returned for
+ BINARY and VARBINARY columns when using
+ DatabaseMetaData.getColumns().
+
+ - ServerPreparedStatement.getBinding() now checks if the statement
+ is closed before attempting to reference the list of parameter
+ bindings, to avoid throwing a NullPointerException.
+
+ - Fixed BUG#13277 - ResultSetMetaData from
+ Statement.getGeneratedKeys() caused NullPointerExceptions to be
+ thrown whenever a method that required a connection reference
+ was called.
+
+ - Removed support for java.nio I/O. Too many implementations
+ turned out to be buggy, and there was no performance difference
+ since MySQL is a blocking protocol anyway.
+
+06-23-05 - Version 3.1.10-stable
+
+ - Fixed connecting without a database specified raised an exception
+ in MysqlIO.changeDatabaseTo().
+
+ - Initial implemention of ParameterMetadata for
+ PreparedStatement.getParameterMetadata(). Only works fully
+ for CallableStatements, as current server-side prepared statements
+ return every parameter as a VARCHAR type.
+
+ - Fixed BUG#11552 - Server-side prepared statements return incorrect
+ values for unsigned TINYINT, SMALLINT, INT and Long.
+
+ - Fixed BUG#11540 - Incorrect year conversion in setDate(..) for
+ system that use B.E. year in default locale.
+
+06-22-05 - Version 3.1.9-stable
+
+ - Overhaul of character set configuration, everything now
+ lives in a properties file.
+
+ - Driver now correctly uses CP932 if available on the server
+ for Windows-31J, CP932 and MS932 java encoding names,
+ otherwise it resorts to SJIS, which is only a close
+ approximation. Currently only MySQL-5.0.3 and newer (and
+ MySQL-4.1.12 or .13, depending on when the character set
+ gets backported) can reliably support any variant of CP932.
+
+ - Fixed BUG#9064 - com.mysql.jdbc.PreparedStatement.ParseInfo
+ does unnecessary call to toCharArray().
+
+ - Fixed Bug#10144 - Memory leak in ServerPreparedStatement if
+ serverPrepare() fails.
+
+ - Actually write manifest file to correct place so it ends up
+ in the binary jar file.
+
+ - Added "createDatabaseIfNotExist" property (default is "false"),
+ which will cause the driver to ask the server to create the
+ database specified in the URL if it doesn't exist. You must have
+ the appropriate privileges for database creation for this to
+ work.
+
+ - Fixed BUG#10156 - Unsigned SMALLINT treated as signed for ResultSet.getInt(),
+ fixed all cases for UNSIGNED integer values and server-side prepared statements,
+ as well as ResultSet.getObject() for UNSIGNED TINYINT.
+
+ - Fixed BUG#10155, double quotes not recognized when parsing
+ client-side prepared statements.
+
+ - Made enableStreamingResults() visible on
+ com.mysql.jdbc.jdbc2.optional.StatementWrapper.
+
+ - Made ServerPreparedStatement.asSql() work correctly so auto-explain
+ functionality would work with server-side prepared statements.
+
+ - Made JDBC2-compliant wrappers public in order to allow access to
+ vendor extensions.
+
+ - Cleaned up logging of profiler events, moved code to dump a profiler
+ event as a string to com.mysql.jdbc.log.LogUtils so that third
+ parties can use it.
+
+ - DatabaseMetaData.supportsMultipleOpenResults() now returns true. The
+ driver has supported this for some time, DBMD just missed that fact.
+
+ - Fixed BUG#10310 - Driver doesn't support {?=CALL(...)} for calling
+ stored functions. This involved adding support for function retrieval
+ to DatabaseMetaData.getProcedures() and getProcedureColumns() as well.
+
+ - Fixed BUG#10485, SQLException thrown when retrieving YEAR(2)
+ with ResultSet.getString(). The driver will now always treat YEAR types
+ as java.sql.Dates and return the correct values for getString().
+ Alternatively, the "yearIsDateType" connection property can be set to
+ "false" and the values will be treated as SHORTs.
+
+ - The datatype returned for TINYINT(1) columns when "tinyInt1isBit=true"
+ (the default) can be switched between Types.BOOLEAN and Types.BIT
+ using the new configuration property "transformedBitIsBoolean", which
+ defaults to "false". If set to "false" (the default),
+ DatabaseMetaData.getColumns() and ResultSetMetaData.getColumnType()
+ will return Types.BOOLEAN for TINYINT(1) columns. If "true",
+ Types.BOOLEAN will be returned instead. Irregardless of this configuration
+ property, if "tinyInt1isBit" is enabled, columns with the type TINYINT(1)
+ will be returned as java.lang.Boolean instances from
+ ResultSet.getObject(..), and ResultSetMetaData.getColumnClassName()
+ will return "java.lang.Boolean".
+
+ - Fixed BUG#10496 - SQLException is thrown when using property
+ "characterSetResults" with cp932 or eucjpms.
+
+ - Reorganized directory layout, sources now in "src" folder,
+ don't pollute parent directory when building, now output goes
+ to "./build", distribution goes to "./dist".
+
+ - Added support/bug hunting feature that generates .sql test
+ scripts to STDERR when "autoGenerateTestcaseScript" is set
+ to "true".
+
+ - Fixed BUG#10850 - 0-length streams not sent to server when
+ using server-side prepared statements.
+
+ - Setting "cachePrepStmts=true" now causes the Connection to also
+ cache the check the driver performs to determine if a prepared
+ statement can be server-side or not, as well as caches server-side
+ prepared statements for the lifetime of a connection. As before,
+ the "prepStmtCacheSize" parameter controls the size of these
+ caches.
+
+ - Try to handle OutOfMemoryErrors more gracefully. Although not
+ much can be done, they will in most cases close the connection
+ they happened on so that further operations don't run into
+ a connection in some unknown state. When an OOM has happened,
+ any further operations on the connection will fail with a
+ "Connection closed" exception that will also list the OOM exception
+ as the reason for the implicit connection close event.
+
+ - Don't send COM_RESET_STMT for each execution of a server-side
+ prepared statement if it isn't required.
+
+ - Driver detects if you're running MySQL-5.0.7 or later, and does
+ not scan for "LIMIT ?[,?]" in statements being prepared, as the
+ server supports those types of queries now.
+
+ - Fixed BUG#11115, Varbinary data corrupted when using server-side
+ prepared statements and ResultSet.getBytes().
+
+ - Connection.setCatalog() is now aware of the "useLocalSessionState"
+ configuration property, which when set to true will prevent
+ the driver from sending "USE ..." to the server if the requested
+ catalog is the same as the current catalog.
+
+ - Added the following configuration bundles, use one or many via
+ the "useConfigs" configuration property:
+
+ * maxPerformance -- maximum performance without being reckless
+ * solarisMaxPerformance -- maximum performance for Solaris,
+ avoids syscalls where it can
+ * 3-0-Compat -- Compatibility with Connector/J 3.0.x functionality
+
+ - Added "maintainTimeStats" configuration property (defaults to "true"),
+ which tells the driver whether or not to keep track of the last query time
+ and the last successful packet sent to the server's time. If set to
+ false, removes two syscalls per query.
+
+ - Fixed BUG#11259, autoReconnect ping causes exception on connection
+ startup.
+
+ - Fixed BUG#11360 Connector/J dumping query into SQLException twice
+
+ - Fixed PreparedStatement.setClob() not accepting null as a parameter.
+
+ - Fixed BUG#11411 - Production package doesn't include JBoss integration
+ classes.
+
+ - Removed nonsensical "costly type conversion" warnings when using
+ usage advisor.
+
+04-14-05 - Version 3.1.8-stable
+
+ - Fixed DatabaseMetaData.getTables() returning views when they were
+ not asked for as one of the requested table types.
+
+ - Added support for new precision-math DECIMAL type in MySQL >= 5.0.3.
+
+ - Fixed ResultSet.getTime() on a NULL value for server-side prepared
+ statements throws NPE.
+
+ - Made Connection.ping() a public method.
+
+ - Fixed Bug#8868, DATE_FORMAT() queries returned as BLOBs from getObject().
+
+ - ServerPreparedStatements now correctly 'stream' BLOB/CLOB data to the
+ server. You can configure the threshold chunk size using the
+ JDBC URL property 'blobSendChunkSize' (the default is one megabyte).
+
+ - BlobFromLocator now uses correct identifier quoting when generating
+ prepared statements.
+
+ - Server-side session variables can be preset at connection time by
+ passing them as a comma-delimited list for the connection property
+ 'sessionVariables'.
+
+ - Fixed regression in ping() for users using autoReconnect=true.
+
+ - Fixed BUG#9040 - PreparedStatement.addBatch() doesn't work with server-side
+ prepared statements and streaming BINARY data.
+
+ - Fixed BUG#8800 - DBMD.supportsMixedCase*Identifiers() returns wrong
+ value on servers running on case-sensitive filesystems.
+
+ - Fixed BUG#9206, can not use 'UTF-8' for characterSetResults
+ configuration property.
+
+ - Fixed BUG#9236, a continuation of BUG#8868, where functions used in queries
+ that should return non-string types when resolved by temporary tables suddenly
+ become opaque binary strings (work-around for server limitation). Also fixed
+ fields with type of CHAR(n) CHARACTER SET BINARY to return correct/matching
+ classes for RSMD.getColumnClassName() and ResultSet.getObject().
+
+ - Fixed BUG#8792 - DBMD.supportsResultSetConcurrency() not returning
+ true for forward-only/read-only result sets (we obviously support this).
+
+ - Fixed BUG#8803, 'DATA_TYPE' column from DBMD.getBestRowIdentifier()
+ causes ArrayIndexOutOfBoundsException when accessed (and in fact, didn't
+ return any value).
+
+ - Check for empty strings ('') when converting char/varchar column data to numbers,
+ throw exception if 'emptyStringsConvertToZero' configuration property is set
+ to 'false' (for backwards-compatibility with 3.0, it is now set to 'true'
+ by default, but will most likely default to 'false' in 3.2).
+
+ - Fixed BUG#9320 - PreparedStatement.getMetaData() inserts blank row in database
+ under certain conditions when not using server-side prepared statements.
+
+ - Connection.canHandleAsPreparedStatement() now makes 'best effort' to distinguish
+ LIMIT clauses with placeholders in them from ones without in order to have fewer
+ false positives when generating work-arounds for statements the server cannot
+ currently handle as server-side prepared statements.
+
+ - Fixed build.xml to not compile log4j logging if log4j not available.
+
+ - Added support for the c3p0 connection pool's (http://c3p0.sf.net/)
+ validation/connection checker interface which uses the lightweight
+ 'COM_PING' call to the server if available. To use it, configure your
+ c3p0 connection pool's 'connectionTesterClassName' property to use
+ 'com.mysql.jdbc.integration.c3p0.MysqlConnectionTester'.
+
+ - Better detection of LIMIT inside/outside of quoted strings so that
+ the driver can more correctly determine whether a prepared statement
+ can be prepared on the server or not.
+
+ - Fixed BUG#9319 - Stored procedures with same name in
+ different databases confuse the driver when it tries to determine
+ parameter counts/types.
+
+ - Added finalizers to ResultSet and Statement implementations to be JDBC
+ spec-compliant, which requires that if not explicitly closed, these
+ resources should be closed upon garbage collection.
+
+ - Fixed BUG#9682 - Stored procedures with DECIMAL parameters with
+ storage specifications that contained "," in them would fail.
+
+ - PreparedStatement.setObject(int, Object, int type, int scale) now
+ uses scale value for BigDecimal instances.
+
+ - Fixed BUG#9704 - Statement.getMoreResults() could throw NPE when
+ existing result set was .close()d.
+
+ - The performance metrics feature now gathers information about
+ number of tables referenced in a SELECT.
+
+ - The logging system is now automatically configured. If the value has
+ been set by the user, via the URL property "logger" or the system
+ property "com.mysql.jdbc.logger", then use that, otherwise, autodetect
+ it using the following steps:
+
+ Log4j, if it's available,
+ Then JDK1.4 logging,
+ Then fallback to our STDERR logging.
+
+ - Fixed BUG#9778, DBMD.getTables() shouldn't return tables if views
+ are asked for, even if the database version doesn't support views.
+
+ - Fixed driver not returning 'true' for '-1' when ResultSet.getBoolean()
+ was called on result sets returned from server-side prepared statements.
+
+ - Added a Manifest.MF file with implementation information to the .jar
+ file.
+
+ - More tests in Field.isOpaqueBinary() to distinguish opaque binary (i.e.
+ fields with type CHAR(n) and CHARACTER SET BINARY) from output of
+ various scalar and aggregate functions that return strings.
+
+ - Fixed BUG#9917 - Should accept null for catalog (meaning use current)
+ in DBMD methods, even though it's not JDBC-compliant for legacy's sake.
+ Disable by setting connection property "nullCatalogMeansCurrent" to "false"
+ (which will be the default value in C/J 3.2.x).
+
+ - Fixed BUG#9769 - Should accept null for name patterns in DBMD (meaning "%"),
+ even though it isn't JDBC compliant, for legacy's sake. Disable by setting
+ connection property "nullNamePatternMatchesAll" to "false" (which will be
+ the default value in C/J 3.2.x).
+
+02-18-05 - Version 3.1.7-stable
+
+
+ - Fixed BUG#7686, Timestamp key column data needed "_binary'"
+ stripped for UpdatableResultSet.refreshRow().
+
+ - Fixed BUG#7715 - Timestamps converted incorrectly to strings
+ with Server-side prepared statements and updatable result sets.
+
+ - Detect new sql_mode variable in string form (it used to be
+ integer) and adjust quoting method for strings appropriately.
+
+ - Added 'holdResultsOpenOverStatementClose' property (default is
+ false), that keeps result sets open over statement.close() or new
+ execution on same statement (suggested by Kevin Burton).
+
+ - Fixed BUG#7952 -- Infinite recursion when 'falling back' to master
+ in failover configuration.
+
+ - Disable multi-statements (if enabled) for MySQL-4.1 versions prior
+ to version 4.1.10 if the query cache is enabled, as the server
+ returns wrong results in this configuration.
+
+ - Fixed duplicated code in configureClientCharset() that prevented
+ useOldUTF8Behavior=true from working properly.
+
+ - Removed 'dontUnpackBinaryResults' functionality, the driver now
+ always stores results from server-side prepared statements as-is
+ from the server and unpacks them on demand.
+
+ - Fixed BUG#8096 where emulated locators corrupt binary data
+ when using server-side prepared statements.
+
+ - Fixed synchronization issue with
+ ServerPreparedStatement.serverPrepare() that could cause
+ deadlocks/crashes if connection was shared between threads.
+
+ - By default, the driver now scans SQL you are preparing via all
+ variants of Connection.prepareStatement() to determine if it is a
+ supported type of statement to prepare on the server side, and if
+ it is not supported by the server, it instead prepares it as a
+ client-side emulated prepared statement (BUG#4718). You can
+ disable this by passing 'emulateUnsupportedPstmts=false' in your
+ JDBC URL.
+
+ - Remove _binary introducer from parameters used as in/out
+ parameters in CallableStatement.
+
+ - Always return byte[]s for output parameters registered as *BINARY.
+
+ - Send correct value for 'boolean' "true" to server for
+ PreparedStatement.setObject(n, "true", Types.BIT).
+
+ - Fixed bug with Connection not caching statements from
+ prepareStatement() when the statement wasn't a server-side
+ prepared statement.
+
+ - Choose correct 'direction' to apply time adjustments when both
+ client and server are in GMT timezone when using
+ ResultSet.get(..., cal) and PreparedStatement.set(...., cal).
+
+ - Added 'dontTrackOpenResources' option (default is false, to be
+ JDBC compliant), which helps with memory use for non-well-behaved
+ apps (i.e applications which don't close Statements when they
+ should).
+
+ - Fixed BUG#8428 - ResultSet.getString() doesn't maintain format
+ stored on server, bug fix only enabled when 'noDatetimeStringSync'
+ property is set to 'true' (the default is 'false').
+
+ - Fixed NPE in ResultSet.realClose() when using usage advisor and
+ result set was already closed.
+
+ - Fixed BUG#8487 - PreparedStatements not creating streaming result
+ sets.
+
+ - Don't pass NULL to String.valueOf() in
+ ResultSet.getNativeConvertToString(), as it stringifies it (i.e.
+ returns "null"), which is not correct for the method in question.
+
+ - Fixed BUG#8484 - ResultSet.getBigDecimal() throws exception
+ when rounding would need to occur to set scale. The driver now
+ chooses a rounding mode of 'half up' if non-rounding
+ BigDecimal.setScale() fails.
+
+ - Added 'useLocalSessionState' configuration property, when set to
+ 'true' the JDBC driver trusts that the application is well-behaved
+ and only sets autocommit and transaction isolation levels using
+ the methods provided on java.sql.Connection, and therefore can
+ manipulate these values in many cases without incurring
+ round-trips to the database server.
+
+ - Added enableStreamingResults() to Statement for connection pool
+ implementations that check Statement.setFetchSize() for
+ specification-compliant values. Call Statement.setFetchSize(>=0)
+ to disable the streaming results for that statement.
+
+ - Added support for BIT type in MySQL-5.0.3. The driver will treat
+ BIT(1-8) as the JDBC standard BIT type (which maps to
+ java.lang.Boolean), as the server does not currently send enough
+ information to determine the size of a bitfield when < 9 bits are
+ declared. BIT(>9) will be treated as VARBINARY, and will return
+ byte[] when getObject() is called.
+
+12-23-04 - Version 3.1.6-stable
+
+ - Fixed hang on SocketInputStream.read() with Statement.setMaxRows() and
+ multiple result sets when driver has to truncate result set directly,
+ rather than tacking a 'LIMIT n' on the end of it.
+
+ - Fixed BUG#7026 - DBMD.getProcedures() doesn't respect catalog parameter.
+
+ - Respect bytes-per-character for RSMD.getPrecision().
+
+12-02-04 - Version 3.1.5-gamma
+
+ - Fix comparisons made between string constants and dynamic strings that
+ are either toUpperCase()d or toLowerCase()d to use Locale.ENGLISH, as
+ some locales 'override' case rules for English. Also use
+ StringUtils.indexOfIgnoreCase() instead of .toUpperCase().indexOf(),
+ avoids creating a very short-lived transient String instance.
+
+ - Fixed BUG#5235 - Server-side prepared statements did not honor
+ 'zeroDateTimeBehavior' property, and would cause class-cast
+ exceptions when using ResultSet.getObject(), as the all-zero string
+ was always returned.
+
+ - Fixed batched updates with server prepared statements weren't looking if
+ the types had changed for a given batched set of parameters compared
+ to the previous set, causing the server to return the error
+ 'Wrong arguments to mysql_stmt_execute()'.
+
+ - Handle case when string representation of timestamp contains trailing '.'
+ with no numbers following it.
+
+ - Fixed BUG#5706 - Inefficient detection of pre-existing string instances
+ in ResultSet.getNativeString().
+
+ - Don't throw exceptions for Connection.releaseSavepoint().
+
+ - Use a per-session Calendar instance by default when decoding dates
+ from ServerPreparedStatements (set to old, less performant behavior by
+ setting property 'dynamicCalendars=true').
+
+ - Added experimental configuration property 'dontUnpackBinaryResults',
+ which delays unpacking binary result set values until they're asked for,
+ and only creates object instances for non-numerical values (it is set
+ to 'false' by default). For some usecase/jvm combinations, this is
+ friendlier on the garbage collector.
+
+ - Fixed BUG#5729 - UNSIGNED BIGINT unpacked incorrectly from
+ server-side prepared statement result sets.
+
+ - Fixed BUG#6225 - ServerSidePreparedStatement allocating short-lived
+ objects un-necessarily.
+
+ - Removed un-wanted new Throwable() in ResultSet constructor due to bad
+ merge (caused a new object instance that was never used for every result
+ set created) - Found while profiling for BUG#6359.
+
+ - Fixed too-early creation of StringBuffer in EscapeProcessor.escapeSQL(),
+ also return String when escaping not needed (to avoid unnecssary object
+ allocations). Found while profiling for BUG#6359.
+
+ - Use null-safe-equals for key comparisons in updatable result sets.
+
+ - Fixed BUG#6537, SUM() on Decimal with server-side prepared statement ignores
+ scale if zero-padding is needed (this ends up being due to conversion to DOUBLE
+ by server, which when converted to a string to parse into BigDecimal, loses all
+ 'padding' zeros).
+
+ - Use DatabaseMetaData.getIdentifierQuoteString() when building DBMD
+ queries.
+
+ - Use 1MB packet for sending file for LOAD DATA LOCAL INFILE if that
+ is < 'max_allowed_packet' on server.
+
+ - Fixed BUG#6399, ResultSetMetaData.getColumnDisplaySize() returns incorrect
+ values for multibyte charsets.
+
+ - Make auto-deserialization of java.lang.Objects stored in BLOBs
+ configurable via 'autoDeserialize' property (defaults to 'false').
+
+ - Re-work Field.isOpaqueBinary() to detect 'CHAR(n) CHARACTER SET BINARY'
+ to support fixed-length binary fields for ResultSet.getObject().
+
+ - Use our own implementation of buffered input streams to get around
+ blocking behavior of java.io.BufferedInputStream. Disable this with
+ 'useReadAheadInput=false'.
+
+ - Fixed BUG#6348, failing to connect to the server when one of the
+ addresses for the given host name is IPV6 (which the server does
+ not yet bind on). The driver now loops through _all_ IP addresses
+ for a given host, and stops on the first one that accepts() a
+ socket.connect().
+
+09-04-04 - Version 3.1.4-beta
+
+ - Fixed BUG#4510 - connector/j 3.1.3 beta does not handle integers
+ correctly (caused by changes to support unsigned reads in
+ Buffer.readInt() -> Buffer.readShort()).
+
+ - Added support in DatabaseMetaData.getTables() and getTableTypes()
+ for VIEWs which are now available in MySQL server version 5.0.x.
+
+ - Fixed BUG#4642 -- ServerPreparedStatement.execute*() sometimes
+ threw ArrayIndexOutOfBoundsException when unpacking field metadata.
+
+ - Optimized integer number parsing, enable 'old' slower integer parsing
+ using JDK classes via 'useFastIntParsing=false' property.
+
+ - Added 'useOnlyServerErrorMessages' property, which causes message text
+ in exceptions generated by the server to only contain the text sent by
+ the server (as opposed to the SQLState's 'standard' description, followed
+ by the server's error message). This property is set to 'true' by default.
+
+ - Fixed BUG#4689 - ResultSet.wasNull() does not work for primatives if a
+ previous null was returned.
+
+ - Track packet sequence numbers if enablePacketDebug=true, and throw an
+ exception if packets received out-of-order.
+
+ - Fixed BUG#4482, ResultSet.getObject() returns wrong type for strings
+ when using prepared statements.
+
+ - Calling MysqlPooledConnection.close() twice (even though an application
+ error), caused NPE. Fixed.
+
+ - Fixed BUG#5012 -- ServerPreparedStatements dealing with return of
+ DECIMAL type don't work.
+
+ - Fixed BUG#5032 -- ResultSet.getObject() doesn't return
+ type Boolean for pseudo-bit types from prepared statements on 4.1.x
+ (shortcut for avoiding extra type conversion when using binary-encoded
+ result sets obscurred test in getObject() for 'pseudo' bit type)
+
+ - You can now use URLs in 'LOAD DATA LOCAL INFILE' statements, and the
+ driver will use Java's built-in handlers for retreiving the data and
+ sending it to the server. This feature is not enabled by default,
+ you must set the 'allowUrlInLocalInfile' connection property to 'true'.
+
+ - The driver is more strict about truncation of numerics on
+ ResultSet.get*(), and will throw a SQLException when truncation is
+ detected. You can disable this by setting 'jdbcCompliantTruncation' to
+ false (it is enabled by default, as this functionality is required
+ for JDBC compliance).
+
+ - Added three ways to deal with all-zero datetimes when reading them from
+ a ResultSet, 'exception' (the default), which throws a SQLException
+ with a SQLState of 'S1009', 'convertToNull', which returns NULL instead of
+ the date, and 'round', which rounds the date to the nearest closest value
+ which is '0001-01-01'.
+
+ - Fixed ServerPreparedStatement to read prepared statement metadata off
+ the wire, even though it's currently a placeholder instead of using
+ MysqlIO.clearInputStream() which didn't work at various times because
+ data wasn't available to read from the server yet. This fixes sporadic
+ errors users were having with ServerPreparedStatements throwing
+ ArrayIndexOutOfBoundExceptions.
+
+ - Use com.mysql.jdbc.Message's classloader when loading resource bundle,
+ should fix sporadic issues when the caller's classloader can't locate
+ the resource bundle.
+
+07-07-04 - Version 3.1.3-beta
+
+ - Mangle output parameter names for CallableStatements so they
+ will not clash with user variable names.
+
+ - Added support for INOUT parameters in CallableStatements.
+
+ - Fix for BUG#4119, null bitmask sent for server-side prepared
+ statements was incorrect.
+
+ - Use SQL Standard SQL states by default, unless 'useSqlStateCodes'
+ property is set to 'false'.
+
+ - Added packet debuging code (see the 'enablePacketDebug' property
+ documentation).
+
+ - Added constants for MySQL error numbers (publicly-accessible,
+ see com.mysql.jdbc.MysqlErrorNumbers), and the ability to
+ generate the mappings of vendor error codes to SQLStates
+ that the driver uses (for documentation purposes).
+
+ - Externalized more messages (on-going effort).
+
+ - Fix for BUG#4311 - Error in retrieval of mediumint column with
+ prepared statements and binary protocol.
+
+ - Support new timezone variables in MySQL-4.1.3 when
+ 'useTimezone=true'
+
+ - Support for unsigned numerics as return types from prepared statements.
+ This also causes a change in ResultSet.getObject() for the 'bigint unsigned'
+ type, which used to return BigDecimal instances, it now returns instances
+ of java.lang.BigInteger.
+
+06-09-04 - Version 3.1.2-alpha
+
+ - Fixed stored procedure parameter parsing info when size was
+ specified for a parameter (i.e. char(), varchar()).
+
+ - Enabled callable statement caching via 'cacheCallableStmts'
+ property.
+
+ - Fixed case when no output parameters specified for a
+ stored procedure caused a bogus query to be issued
+ to retrieve out parameters, leading to a syntax error
+ from the server.
+
+ - Fixed case when no parameters could cause a NullPointerException
+ in CallableStatement.setOutputParameters().
+
+ - Removed wrapping of exceptions in MysqlIO.changeUser().
+
+ - Fixed sending of split packets for large queries, enabled nio
+ ability to send large packets as well.
+
+ - Added .toString() functionality to ServerPreparedStatement,
+ which should help if you're trying to debug a query that is
+ a prepared statement (it shows SQL as the server would process).
+
+ - Added 'gatherPerformanceMetrics' property, along with properties
+ to control when/where this info gets logged (see docs for more
+ info).
+
+ - ServerPreparedStatements weren't actually de-allocating
+ server-side resources when .close() was called.
+
+ - Added 'logSlowQueries' property, along with property
+ 'slowQueriesThresholdMillis' to control when a query should
+ be considered 'slow'.
+
+ - Correctly map output parameters to position given in
+ prepareCall() vs. order implied during registerOutParameter() -
+ fixes BUG#3146.
+
+ - Correctly detect initial character set for servers >= 4.1.0
+
+ - Cleaned up detection of server properties.
+
+ - Support placeholder for parameter metadata for server >= 4.1.2
+
+ - Fix for BUG#3539 getProcedures() does not return any procedures in
+ result set
+
+ - Fix for BUG#3540 getProcedureColumns() doesn't work with wildcards
+ for procedure name
+
+ - Fixed BUG#3520 -- DBMD.getSQLStateType() returns incorrect value.
+
+ - Added 'connectionCollation' property to cause driver to issue
+ 'set collation_connection=...' query on connection init if default
+ collation for given charset is not appropriate.
+
+ - Fixed DatabaseMetaData.getProcedures() when run on MySQL-5.0.0 (output of
+ 'show procedure status' changed between 5.0.1 and 5.0.0.
+
+ - Fixed BUG#3804 -- getWarnings() returns SQLWarning instead of DataTruncation
+
+ - Don't enable server-side prepared statements for server version 5.0.0 or 5.0.1,
+ as they aren't compatible with the '4.1.2+' style that the driver uses (the driver
+ expects information to come back that isn't there, so it hangs).
+
+
+02-14-04 - Version 3.1.1-alpha
+
+ - Fixed bug with UpdatableResultSets not using client-side
+ prepared statements.
+
+ - Fixed character encoding issues when converting bytes to
+ ASCII when MySQL doesn't provide the character set, and
+ the JVM is set to a multibyte encoding (usually affecting
+ retrieval of numeric values).
+
+ - Unpack 'unknown' data types from server prepared statements
+ as Strings.
+
+ - Implemented long data (Blobs, Clobs, InputStreams, Readers)
+ for server prepared statements.
+
+ - Implemented Statement.getWarnings() for MySQL-4.1 and newer
+ (using 'SHOW WARNINGS').
+
+ - Default result set type changed to TYPE_FORWARD_ONLY
+ (JDBC compliance).
+
+ - Centralized setting of result set type and concurrency.
+
+ - Re-factored how connection properties are set and exposed
+ as DriverPropertyInfo as well as Connection and DataSource
+ properties.
+
+ - Support for NIO. Use 'useNIO=true' on platforms that support
+ NIO.
+
+ - Support for SAVEPOINTs (MySQL >= 4.0.14 or 4.1.1).
+
+ - Support for mysql_change_user()...See the changeUser() method
+ in com.mysql.jdbc.Connection.
+
+ - Reduced number of methods called in average query to be more
+ efficient.
+
+ - Prepared Statements will be re-prepared on auto-reconnect. Any errors
+ encountered are postponed until first attempt to re-execute the
+ re-prepared statement.
+
+ - Ensure that warnings are cleared before executing queries
+ on prepared statements, as-per JDBC spec (now that we support
+ warnings).
+
+ - Support 'old' profileSql capitalization in ConnectionProperties.
+ This property is deprecated, you should use 'profileSQL' if possible.
+
+ - Optimized Buffer.readLenByteArray() to return shared empty byte array
+ when length is 0.
+
+ - Allow contents of PreparedStatement.setBlob() to be retained
+ between calls to .execute*().
+
+ - Deal with 0-length tokens in EscapeProcessor (caused by callable
+ statement escape syntax).
+
+ - Check for closed connection on delete/update/insert row operations in
+ UpdatableResultSet.
+
+ - Fix support for table aliases when checking for all primary keys in
+ UpdatableResultSet.
+
+ - Removed useFastDates connection property.
+
+ - Correctly initialize datasource properties from JNDI Refs, including
+ explicitly specified URLs.
+
+ - DatabaseMetaData now reports supportsStoredProcedures() for
+ MySQL versions >= 5.0.0
+
+ - Fixed stack overflow in Connection.prepareCall() (bad merge).
+
+ - Fixed IllegalAccessError to Calendar.getTimeInMillis() in DateTimeValue
+ (for JDK < 1.4).
+
+ - Fix for BUG#1673, where DatabaseMetaData.getColumns() is not
+ returning correct column ordinal info for non '%' column name patterns.
+
+ - Merged fix of datatype mapping from MySQL type 'FLOAT' to
+ java.sql.Types.REAL from 3.0 branch.
+
+ - Detect collation of column for RSMD.isCaseSensitive().
+
+ - Fixed sending of queries > 16M.
+
+ - Added named and indexed input/output parameter support to CallableStatement.
+ MySQL-5.0.x or newer.
+
+ - Fixed NullPointerException in ServerPreparedStatement.setTimestamp(),
+ as well as year and month descrepencies in
+ ServerPreparedStatement.setTimestamp(), setDate().
+
+ - Added ability to have multiple database/JVM targets for compliance
+ and regression/unit tests in build.xml.
+
+ - Fixed NPE and year/month bad conversions when accessing some
+ datetime functionality in ServerPreparedStatements and their
+ resultant result sets.
+
+ - Display where/why a connection was implicitly closed (to
+ aid debugging).
+
+ - CommunicationsException implemented, that tries to determine
+ why communications was lost with a server, and displays
+ possible reasons when .getMessage() is called.
+
+ - Fixed BUG#2359, NULL values for numeric types in binary
+ encoded result sets causing NullPointerExceptions.
+
+ - Implemented Connection.prepareCall(), and DatabaseMetaData.
+ getProcedures() and getProcedureColumns().
+
+ - Reset 'long binary' parameters in ServerPreparedStatement when
+ clearParameters() is called, by sending COM_RESET_STMT to the
+ server.
+
+ - Merged prepared statement caching, and .getMetaData() support
+ from 3.0 branch.
+
+ - Fixed off-by-1900 error in some cases for
+ years in TimeUtil.fastDate/TimeCreate() when unpacking results
+ from server-side prepared statements.
+
+ - Fixed BUG#2502 -- charset conversion issue in getTables().
+
+ - Implemented multiple result sets returned from a statement
+ or stored procedure.
+
+ - Fixed BUG#2606 -- Server side prepared statements not returning
+ datatype 'YEAR' correctly.
+
+ - Enabled streaming of result sets from server-side prepared
+ statements.
+
+ - Fixed BUG#2623 -- Class-cast exception when using
+ scrolling result sets and server-side prepared statements.
+
+ - Merged unbuffered input code from 3.0.
+
+ - Fixed ConnectionProperties that weren't properly exposed
+ via accessors, cleaned up ConnectionProperties code.
+
+ - Fixed BUG#2671, NULL fields not being encoded correctly in
+ all cases in server side prepared statements.
+
+ - Fixed rare buffer underflow when writing numbers into buffers
+ for sending prepared statement execution requests.
+
+ - Use DocBook version of docs for shipped versions of drivers.
+
+
+02-18-03 - Version 3.1.0-alpha
+
+ - Added 'requireSSL' property.
+
+ - Added 'useServerPrepStmts' property (default 'false'). The
+ driver will use server-side prepared statements when the
+ server version supports them (4.1 and newer) when this
+ property is set to 'true'. It is currently set to 'false'
+ by default until all bind/fetch functionality has been
+ implemented. Currently only DML prepared statements are
+ implemented for 4.1 server-side prepared statements.
+
+ - Track open Statements, close all when Connection.close()
+ is called (JDBC compliance).
+
+06-22-05 - Version 3.0.17-ga
+
+ - Fixed BUG#5874, Timestamp/Time conversion goes in the wrong 'direction'
+ when useTimeZone='true' and server timezone differs from client timezone.
+
+ - Fixed BUG#7081, DatabaseMetaData.getIndexInfo() ignoring 'unique'
+ parameter.
+
+ - Support new protocol type 'MYSQL_TYPE_VARCHAR'.
+
+ - Added 'useOldUTF8Behavoior' configuration property, which causes
+ JDBC driver to act like it did with MySQL-4.0.x and earlier when
+ the character encoding is 'utf-8' when connected to MySQL-4.1 or
+ newer.
+
+ - Fixed BUG#7316 - Statements created from a pooled connection were
+ returning physical connection instead of logical connection when
+ getConnection() was called.
+
+ - Fixed BUG#7033 - PreparedStatements don't encode Big5 (and other
+ multibyte) character sets correctly in static SQL strings.
+
+ - Fixed BUG#6966, connections starting up failed-over (due to down master)
+ never retry master.
+
+ - Fixed BUG#7061, PreparedStatement.fixDecimalExponent() adding extra
+ '+', making number unparseable by MySQL server.
+
+ - Fixed BUG#7686, Timestamp key column data needed "_binary'" stripped for
+ UpdatableResultSet.refreshRow().
+
+ - Backported SQLState codes mapping from Connector/J 3.1, enable with
+ 'useSqlStateCodes=true' as a connection property, it defaults to
+ 'false' in this release, so that we don't break legacy applications (it
+ defaults to 'true' starting with Connector/J 3.1).
+
+ - Fixed BUG#7601, PreparedStatement.fixDecimalExponent() adding extra
+ '+', making number unparseable by MySQL server.
+
+ - Escape sequence {fn convert(..., type)} now supports ODBC-style types
+ that are prepended by 'SQL_'.
+
+ - Fixed duplicated code in configureClientCharset() that prevented
+ useOldUTF8Behavior=true from working properly.
+
+ - Handle streaming result sets with > 2 billion rows properly by fixing
+ wraparound of row number counter.
+
+ - Fixed BUG#7607 - MS932, SHIFT_JIS and Windows_31J not recog. as
+ aliases for sjis.
+
+ - Fixed BUG#6549 (while fixing #7607), adding 'CP943' to aliases for
+ sjis.
+
+ - Fixed BUG#8064, which requires hex escaping of binary data when using
+ multibyte charsets with prepared statements.
+
+ - Fixed BUG#8812, NON_UNIQUE column from DBMD.getIndexInfo() returned
+ inverted value.
+
+ - Workaround for server BUG#9098 - default values of CURRENT_* for
+ DATE/TIME/TIMESTAMP/TIMESTAMP columns can't be distinguished from
+ 'string' values, so UpdatableResultSet.moveToInsertRow() generates
+ bad SQL for inserting default values.
+
+ - Fixed BUG#8629 - 'EUCKR' charset is sent as 'SET NAMES euc_kr' which
+ MySQL-4.1 and newer doesn't understand.
+
+ - DatabaseMetaData.supportsSelectForUpdate() returns correct value based
+ on server version.
+
+ - Use hex escapes for PreparedStatement.setBytes() for double-byte charsets
+ including 'aliases' Windows-31J, CP934, MS932.
+
+ - Added support for the "EUC_JP_Solaris" character encoding, which maps
+ to a MySQL encoding of "eucjpms" (backported from 3.1 branch). This only
+ works on servers that support eucjpms, namely 5.0.3 or later.
+
+11-15-04 - Version 3.0.16-ga
+
+ - Re-issue character set configuration commands when re-using pooled
+ connections and/or Connection.changeUser() when connected to MySQL-4.1
+ or newer.
+
+ - Fixed ResultSetMetaData.isReadOnly() to detect non-writable columns
+ when connected to MySQL-4.1 or newer, based on existence of 'original'
+ table and column names.
+
+ - Fixed BUG#5664, ResultSet.updateByte() when on insert row
+ throws ArrayOutOfBoundsException.
+
+ - Fixed DatabaseMetaData.getTypes() returning incorrect (i.e. non-negative)
+ scale for the 'NUMERIC' type.
+
+ - Fixed BUG#6198, off-by-one bug in Buffer.readString(string).
+
+ - Made TINYINT(1) -> BIT/Boolean conversion configurable via 'tinyInt1isBit'
+ property (default 'true' to be JDBC compliant out of the box).
+
+ - Only set 'character_set_results' during connection establishment if
+ server version >= 4.1.1.
+
+ - Fixed regression where useUnbufferedInput was defaulting to 'false'.
+
+ - Fixed BUG#6231, ResultSet.getTimestamp() on a column with TIME in it
+ fails.
+
+09-04-04 - Version 3.0.15-ga
+
+ - Fixed BUG#4010 - StringUtils.escapeEasternUnicodeByteStream is still
+ broken for GBK
+
+ - Fixed BUG#4334 - Failover for autoReconnect not using port #'s for any
+ hosts, and not retrying all hosts. (WARN: This required a change to
+ the SocketFactory connect() method signature, which is now
+
+ public Socket connect(String host, int portNumber, Properties props),
+
+ therefore any third-party socket factories will have to be changed
+ to support this signature.
+
+ - Logical connections created by MysqlConnectionPoolDataSource will
+ now issue a rollback() when they are closed and sent back to the pool.
+ If your application server/connection pool already does this for you, you
+ can set the 'rollbackOnPooledClose' property to false to avoid the
+ overhead of an extra rollback().
+
+ - Removed redundant calls to checkRowPos() in ResultSet.
+
+ - Fixed BUG#4742, 'DOUBLE' mapped twice in DBMD.getTypeInfo().
+
+ - Added FLOSS license exemption.
+
+ - Fixed BUG#4808, calling .close() twice on a PooledConnection causes NPE.
+
+ - Fixed BUG#4138 and BUG#4860, DBMD.getColumns() returns incorrect JDBC
+ type for unsigned columns. This affects type mappings for all numeric
+ types in the RSMD.getColumnType() and RSMD.getColumnTypeNames() methods
+ as well, to ensure that 'like' types from DBMD.getColumns() match up
+ with what RSMD.getColumnType() and getColumnTypeNames() return.
+
+ - 'Production' - 'GA' in naming scheme of distributions.
+
+ - Fix for BUG#4880, RSMD.getPrecision() returning 0 for non-numeric types
+ (should return max length in chars for non-binary types, max length
+ in bytes for binary types). This fix also fixes mapping of
+ RSMD.getColumnType() and RSMD.getColumnTypeName() for the BLOB types based
+ on the length sent from the server (the server doesn't distinguish between
+ TINYBLOB, BLOB, MEDIUMBLOB or LONGBLOB at the network protocol level).
+
+ - Fixed BUG#5022 - ResultSet should release Field[] instance in .close().
+
+ - Fixed BUG#5069 -- ResultSet.getMetaData() should not return
+ incorrectly-initialized metadata if the result set has been closed, but
+ should instead throw a SQLException. Also fixed for getRow() and
+ getWarnings() and traversal methods by calling checkClosed() before
+ operating on instance-level fields that are nullified during .close().
+
+ - Parse new timezone variables from 4.1.x servers.
+
+ - Use _binary introducer for PreparedStatement.setBytes() and
+ set*Stream() when connected to MySQL-4.1.x or newer to avoid
+ misinterpretation during character conversion.
+
+05-28-04 - Version 3.0.14-production
+
+ - Fixed URL parsing error
+
+05-27-04 - Version 3.0.13-production
+
+ - Fixed BUG#3848 - Using a MySQLDatasource without server name fails
+
+ - Fixed BUG#3920 - "No Database Selected" when using
+ MysqlConnectionPoolDataSource.
+
+ - Fixed BUG#3873 - PreparedStatement.getGeneratedKeys() method returns only
+ 1 result for batched insertions
+
+05-18-04 - Version 3.0.12-production
+
+ - Add unsigned attribute to DatabaseMetaData.getColumns() output
+ in the TYPE_NAME column.
+
+ - Added 'failOverReadOnly' property, to allow end-user to configure
+ state of connection (read-only/writable) when failed over.
+
+ - Backported 'change user' and 'reset server state' functionality
+ from 3.1 branch, to allow clients of MysqlConnectionPoolDataSource
+ to reset server state on getConnection() on a pooled connection.
+
+ - Don't escape SJIS/GBK/BIG5 when using MySQL-4.1 or newer.
+
+ - Allow 'url' parameter for MysqlDataSource and MysqlConnectionPool
+ DataSource so that passing of other properties is possible from
+ inside appservers.
+
+ - Map duplicate key and foreign key errors to SQLState of
+ '23000'.
+
+ - Backport documentation tooling from 3.1 branch.
+
+ - Return creating statement for ResultSets created by
+ getGeneratedKeys() (BUG#2957)
+
+ - Allow java.util.Date to be sent in as parameter to
+ PreparedStatement.setObject(), converting it to a Timestamp
+ to maintain full precision (BUG#3103).
+
+ - Don't truncate BLOBs/CLOBs when using setBytes() and/or
+ setBinary/CharacterStream() (BUG#2670).
+
+ - Dynamically configure character set mappings for field-level
+ character sets on MySQL-4.1.0 and newer using 'SHOW COLLATION'
+ when connecting.
+
+ - Map 'binary' character set to 'US-ASCII' to support DATETIME
+ charset recognition for servers >= 4.1.2
+
+ - Use 'SET character_set_results" during initialization to allow any
+ charset to be returned to the driver for result sets.
+
+ - Use charsetnr returned during connect to encode queries before
+ issuing 'SET NAMES' on MySQL >= 4.1.0.
+
+ - Add helper methods to ResultSetMetaData (getColumnCharacterEncoding()
+ and getColumnCharacterSet()) to allow end-users to see what charset
+ the driver thinks it should be using for the column.
+
+ - Only set character_set_results for MySQL >= 4.1.0.
+
+ - Fixed BUG#3511, StringUtils.escapeSJISByteStream() not covering all
+ eastern double-byte charsets correctly.
+
+ - Renamed StringUtils.escapeSJISByteStream() to more appropriate
+ escapeEasternUnicodeByteStream().
+
+ - Fixed BUG#3554 - Not specifying database in URL caused MalformedURL
+ exception.
+
+ - Auto-convert MySQL encoding names to Java encoding names if used
+ for characterEncoding property.
+
+ - Added encoding names that are recognized on some JVMs to fix case
+ where they were reverse-mapped to MySQL encoding names incorrectly.
+
+ - Use junit.textui.TestRunner for all unit tests (to allow them to be
+ run from the command line outside of Ant or Eclipse).
+
+ - Fixed BUG#3557 - UpdatableResultSet not picking up default values
+ for moveToInsertRow().
+
+ - Fixed BUG#3570 - inconsistent reporting of column type. The server
+ still doesn't return all types for *BLOBs *TEXT correctly, so the
+ driver won't return those correctly.
+
+ - Fixed BUG#3520 -- DBMD.getSQLStateType() returns incorrect value.
+
+ - Fixed regression in PreparedStatement.setString() and eastern character
+ encodings.
+
+ - Made StringRegressionTest 4.1-unicode aware.
+
+02-19-04 - Version 3.0.11-stable
+
+ - Trigger a 'SET NAMES utf8' when encoding is forced to 'utf8' _or_
+ 'utf-8' via the 'characterEncoding' property. Previously, only the
+ Java-style encoding name of 'utf-8' would trigger this.
+
+ - AutoReconnect time was growing faster than exponentially (BUG#2447).
+
+ - Fixed failover always going to last host in list (BUG#2578)
+
+ - Added 'useUnbufferedInput' parameter, and now use it by default
+ (due to JVM issue
+ http://developer.java.sun.com/developer/bugParade/bugs/4401235.html)
+
+ - Detect 'on/off' or '1','2','3' form of lower_case_table_names on
+ server.
+
+ - Return 'java.lang.Integer' for TINYINT and SMALLINT types from
+ ResultSetMetaData.getColumnClassName() (fix for BUG#2852).
+
+ - Return 'java.lang.Double' for FLOAT type from ResultSetMetaData.
+ getColumnClassName() (fix for BUG#2855).
+
+ - Return '[B' instead of java.lang.Object for BINARY, VARBINARY and
+ LONGVARBINARY types from ResultSetMetaData.getColumnClassName()
+ (JDBC compliance).
+
+01-13-04 - Version 3.0.10-stable
+
+ - Don't count quoted id's when inside a 'string' in PreparedStatement
+ parsing (fix for BUG#1511).
+
+ - 'Friendlier' exception message for PacketTooLargeException
+ (BUG#1534).
+
+ - Backported fix for aliased tables and UpdatableResultSets in
+ checkUpdatability() method from 3.1 branch.
+
+ - Fix for ArrayIndexOutOfBounds exception when using Statement.setMaxRows()
+ (BUG#1695).
+
+ - Fixed BUG#1576, dealing with large blobs and split packets not being
+ read correctly.
+
+ - Fixed regression of Statement.getGeneratedKeys() and REPLACE statements.
+
+ - Fixed BUG#1630, subsequent call to ResultSet.updateFoo() causes NPE if
+ result set is not updatable.
+
+ - Fix for 4.1.1-style auth with no password.
+
+ - Fix for BUG#1731, Foreign Keys column sequence is not consistent in
+ DatabaseMetaData.getImported/Exported/CrossReference().
+
+ - Fix for BUG#1775 - DatabaseMetaData.getSystemFunction() returning
+ bad function 'VResultsSion'.
+
+ - Fix for BUG#1592 -- cross-database updatable result sets
+ are not checked for updatability correctly.
+
+ - DatabaseMetaData.getColumns() should return Types.LONGVARCHAR for
+ MySQL LONGTEXT type.
+
+ - ResultSet.getObject() on TINYINT and SMALLINT columns should return
+ Java type 'Integer' (BUG#1913)
+
+ - Added 'alwaysClearStream' connection property, which causes the driver
+ to always empty any remaining data on the input stream before
+ each query.
+
+ - Added more descriptive error message 'Server Configuration Denies
+ Access to DataSource', as well as retrieval of message from server.
+
+ - Autoreconnect code didn't set catalog upon reconnect if it had been
+ changed.
+
+ - Implement ResultSet.updateClob().
+
+ - ResultSetMetaData.isCaseSensitive() returned wrong value for CHAR/VARCHAR
+ columns.
+
+ - Fix for BUG#1933 -- Connection property "maxRows" not honored.
+
+ - Fix for BUG#1925 -- Statements being created too many times in
+ DBMD.extractForeignKeyFromCreateTable().
+
+ - Fix for BUG#1914 -- Support escape sequence {fn convert ... }
+
+ - Fix for BUG#1958 -- ArrayIndexOutOfBounds when parameter number ==
+ number of parameters + 1.
+
+ - Fix for BUG#2006 -- ResultSet.findColumn() should use first matching
+ column name when there are duplicate column names in SELECT query
+ (JDBC-compliance).
+
+ - Removed static synchronization bottleneck from
+ PreparedStatement.setTimestamp().
+
+ - Removed static synchronization bottleneck from instance factory
+ method of SingleByteCharsetConverter.
+
+ - Enable caching of the parsing stage of prepared statements via
+ the 'cachePrepStmts', 'prepStmtCacheSize' and 'prepStmtCacheSqlLimit'
+ properties (disabled by default).
+
+ - Speed up parsing of PreparedStatements, try to use one-pass whenever
+ possible.
+
+ - Fixed security exception when used in Applets (applets can't
+ read the system property 'file.encoding' which is needed
+ for LOAD DATA LOCAL INFILE).
+
+ - Use constants for SQLStates.
+
+ - Map charset 'ko18_ru' to 'ko18r' when connected to MySQL-4.1.0 or
+ newer.
+
+ - Ensure that Buffer.writeString() saves room for the \0.
+
+ - Fixed exception 'Unknown character set 'danish' on connect w/ JDK-1.4.0
+
+ - Fixed mappings in SQLError to report deadlocks with SQLStates of '41000'.
+
+ - 'maxRows' property would affect internal statements, so check it for all
+ statement creation internal to the driver, and set to 0 when it is not.
+
+10-07-03 - Version 3.0.9-stable
+
+ - Faster date handling code in ResultSet and PreparedStatement (no longer
+ uses Date methods that synchronize on static calendars).
+
+ - Fixed test for end of buffer in Buffer.readString().
+
+ - Fixed ResultSet.previous() behavior to move current
+ position to before result set when on first row
+ of result set (bugs.mysql.com BUG#496)
+
+ - Fixed Statement and PreparedStatement issuing bogus queries
+ when setMaxRows() had been used and a LIMIT clause was present
+ in the query.
+
+ - Fixed BUG#661 - refreshRow didn't work when primary key values
+ contained values that needed to be escaped (they ended up being
+ doubly-escaped).
+
+ - Support InnoDB contraint names when extracting foreign key info
+ in DatabaseMetaData BUG#517 and BUG#664
+ (impl. ideas from Parwinder Sekhon)
+
+ - Backported 4.1 protocol changes from 3.1 branch (server-side SQL
+ states, new field info, larger client capability flags,
+ connect-with-database, etc).
+
+ - Fix UpdatableResultSet to return values for getXXX() when on
+ insert row (BUG#675).
+
+ - The insertRow in an UpdatableResultSet is now loaded with
+ the default column values when moveToInsertRow() is called
+ (BUG#688)
+
+ - DatabaseMetaData.getColumns() wasn't returning NULL for
+ default values that are specified as NULL.
+
+ - Change default statement type/concurrency to TYPE_FORWARD_ONLY
+ and CONCUR_READ_ONLY (spec compliance).
+
+ - Don't try and reset isolation level on reconnect if MySQL doesn't
+ support them.
+
+ - Don't wrap SQLExceptions in RowDataDynamic.
+
+ - Don't change timestamp TZ twice if useTimezone==true (BUG#774)
+
+ - Fixed regression in large split-packet handling (BUG#848).
+
+ - Better diagnostic error messages in exceptions for 'streaming'
+ result sets.
+
+ - Issue exception on ResultSet.getXXX() on empty result set (wasn't
+ caught in some cases).
+
+ - Don't hide messages from exceptions thrown in I/O layers.
+
+ - Don't fire connection closed events when closing pooled connections, or
+ on PooledConnection.getConnection() with already open connections (BUG#884).
+
+ - Clip +/- INF (to smallest and largest representative values for the type in
+ MySQL) and NaN (to 0) for setDouble/setFloat(), and issue a warning on the
+ statement when the server does not support +/- INF or NaN.
+
+ - Fix for BUG#879, double-escaping of '\' when charset is SJIS or GBK and '\'
+ appears in non-escaped input.
+
+ - When emptying input stream of unused rows for 'streaming' result sets,
+ have the current thread yield() every 100 rows in order to not monopolize
+ CPU time.
+
+ - Fixed BUG#1099, DatabaseMetaData.getColumns() getting confused about the
+ keyword 'set' in character columns.
+
+ - Fixed deadlock issue with Statement.setMaxRows().
+
+ - Fixed CLOB.truncate(), BUG#1130
+
+ - Optimized CLOB.setChracterStream(), BUG#1131
+
+ - Made databaseName, portNumber and serverName optional parameters
+ for MysqlDataSourceFactory (BUG#1246)
+
+ - Fix for BUG#1247 -- ResultSet.get/setString mashing char 127
+
+ - Backported auth. changes for 4.1.1 and newer from 3.1 branch.
+
+ - Added com.mysql.jdbc.util.BaseBugReport to help creation of testcases
+ for bug reports.
+
+ - Added property to 'clobber' streaming results, by setting the
+ 'clobberStreamingResults' property to 'true' (the default is 'false').
+ This will cause a 'streaming' ResultSet to be automatically
+ closed, and any oustanding data still streaming from the server to
+ be discarded if another query is executed before all the data has been
+ read from the server.
+
+05-23-03 - Version 3.0.8-stable
+
+ - Allow bogus URLs in Driver.getPropertyInfo().
+
+ - Return list of generated keys when using multi-value INSERTS
+ with Statement.getGeneratedKeys().
+
+ - Use JVM charset with filenames and 'LOAD DATA [LOCAL] INFILE'
+
+ - Fix infinite loop with Connection.cleanup().
+
+ - Changed Ant target 'compile-core' to 'compile-driver', and
+ made testsuite compilation a separate target.
+
+ - Fixed result set not getting set for Statement.executeUpdate(),
+ which affected getGeneratedKeys() and getUpdateCount() in
+ some cases.
+
+ - Unicode character 0xFFFF in a string would cause the driver to
+ throw an ArrayOutOfBoundsException (Bug #378)
+
+ - Return correct amount of generated keys when using 'REPLACE'
+ statements.
+
+ - Fix problem detecting server character set in some cases.
+
+ - Fix row data decoding error when using _very_ large packets.
+
+ - Optimized row data decoding.
+
+ - Issue exception when operating on an already-closed
+ prepared statement.
+
+ - Fixed SJIS encoding bug, thanks to Naoto Sato.
+
+ - Optimized usage of EscapeProcessor.
+
+ - Allow multiple calls to Statement.close()
+
+04-08-03 - Version 3.0.7-stable
+
+ - Fixed MysqlPooledConnection.close() calling wrong event type.
+
+ - Fixed StringIndexOutOfBoundsException in PreparedStatement.
+ setClob().
+
+ - 4.1 Column Metadata fixes
+
+ - Remove synchronization from Driver.connect() and
+ Driver.acceptsUrl().
+
+ - IOExceptions during a transaction now cause the Connection to
+ be closed.
+
+ - Fixed missing conversion for 'YEAR' type in ResultSetMetaData.
+ getColumnTypeName().
+
+ - Don't pick up indexes that start with 'pri' as primary keys
+ for DBMD.getPrimaryKeys().
+
+ - Throw SQLExceptions when trying to do operations on a forcefully
+ closed Connection (i.e. when a communication link failure occurs).
+
+ - You can now toggle profiling on/off using
+ Connection.setProfileSql(boolean).
+
+ - Fixed charset issues with database metadata (charset was not
+ getting set correctly).
+
+ - Updatable ResultSets can now be created for aliased tables/columns
+ when connected to MySQL-4.1 or newer.
+
+ - Fixed 'LOAD DATA LOCAL INFILE' bug when file > max_allowed_packet.
+
+ - Fixed escaping of 0x5c ('\') character for GBK and Big5 charsets.
+
+ - Fixed ResultSet.getTimestamp() when underlying field is of type DATE.
+
+ - Ensure that packet size from alignPacketSize() does not
+ exceed MAX_ALLOWED_PACKET (JVM bug)
+
+ - Don't reset Connection.isReadOnly() when autoReconnecting.
+
+02-18-03 - Version 3.0.6-stable
+
+ - Fixed ResultSetMetaData to return "" when catalog not known.
+ Fixes NullPointerExceptions with Sun's CachedRowSet.
+
+ - Fixed DBMD.getTypeInfo() and DBMD.getColumns() returning
+ different value for precision in TEXT/BLOB types.
+
+ - Allow ignoring of warning for 'non transactional tables' during
+ rollback (compliance/usability) by setting 'ignoreNonTxTables'
+ property to 'true'.
+
+ - Fixed SQLExceptions getting swallowed on initial connect.
+
+ - Fixed Statement.setMaxRows() to stop sending 'LIMIT' type queries
+ when not needed (performance)
+
+ - Clean up Statement query/method mismatch tests (i.e. INSERT not
+ allowed with .executeQuery()).
+
+ - More checks added in ResultSet traversal method to catch
+ when in closed state.
+
+ - Fixed ResultSetMetaData.isWritable() to return correct value.
+
+ - Add 'window' of different NULL sorting behavior to
+ DBMD.nullsAreSortedAtStart (4.0.2 to 4.0.10, true, otherwise,
+ no).
+
+ - Implemented Blob.setBytes(). You still need to pass the
+ resultant Blob back into an updatable ResultSet or
+ PreparedStatement to persist the changes, as MySQL does
+ not support 'locators'.
+
+ - Backported 4.1 charset field info changes from Connector/J 3.1
+
+01-22-03 - Version 3.0.5-gamma
+
+ - Fixed Buffer.fastSkipLenString() causing ArrayIndexOutOfBounds
+ exceptions with some queries when unpacking fields.
+
+ - Implemented an empty TypeMap for Connection.getTypeMap() so that
+ some third-party apps work with MySQL (IBM WebSphere 5.0 Connection
+ pool).
+
+ - Added missing LONGTEXT type to DBMD.getColumns().
+
+ - Retrieve TX_ISOLATION from database for
+ Connection.getTransactionIsolation() when the MySQL version
+ supports it, instead of an instance variable.
+
+ - Quote table names in DatabaseMetaData.getColumns(),
+ getPrimaryKeys(), getIndexInfo(), getBestRowIdentifier()
+
+ - Greatly reduce memory required for setBinaryStream() in
+ PreparedStatements.
+
+ - Fixed ResultSet.isBeforeFirst() for empty result sets.
+
+ - Added update options for foreign key metadata.
+
+
+01-06-03 - Version 3.0.4-gamma
+
+ - Added quoted identifiers to database names for
+ Connection.setCatalog.
+
+ - Added support for quoted identifiers in PreparedStatement
+ parser.
+
+ - Streamlined character conversion and byte[] handling in
+ PreparedStatements for setByte().
+
+ - Reduce memory footprint of PreparedStatements by sharing
+ outbound packet with MysqlIO.
+
+ - Added 'strictUpdates' property to allow control of amount
+ of checking for 'correctness' of updatable result sets. Set this
+ to 'false' if you want faster updatable result sets and you know
+ that you create them from SELECTs on tables with primary keys and
+ that you have selected all primary keys in your query.
+
+ - Added support for 4.0.8-style large packets.
+
+ - Fixed PreparedStatement.executeBatch() parameter overwriting.
+
+12-17-02 - Version 3.0.3-dev
+
+ - Changed charsToByte in SingleByteCharConverter to be non-static
+
+ - Changed SingleByteCharConverter to use lazy initialization of each
+ converter.
+
+ - Fixed charset handling in Fields.java
+
+ - Implemented Connection.nativeSQL()
+
+ - More robust escape tokenizer -- recognize '--' comments, and allow
+ nested escape sequences (see testsuite.EscapeProcessingTest)
+
+ - DBMD.getImported/ExportedKeys() now handles multiple foreign keys
+ per table.
+
+ - Fixed ResultSetMetaData.getPrecision() returning incorrect values
+ for some floating point types.
+
+ - Fixed ResultSetMetaData.getColumnTypeName() returning BLOB for
+ TEXT and TEXT for BLOB types.
+
+ - Fixed Buffer.isLastDataPacket() for 4.1 and newer servers.
+
+ - Added CLIENT_LONG_FLAG to be able to get more column flags
+ (isAutoIncrement() being the most important)
+
+ - Because of above, implemented ResultSetMetaData.isAutoIncrement()
+ to use Field.isAutoIncrement().
+
+ - Honor 'lower_case_table_names' when enabled in the server when
+ doing table name comparisons in DatabaseMetaData methods.
+
+ - Some MySQL-4.1 protocol support (extended field info from selects)
+
+ - Use non-aliased table/column names and database names to fullly
+ qualify tables and columns in UpdatableResultSet (requires
+ MySQL-4.1 or newer)
+
+ - Allow user to alter behavior of Statement/
+ PreparedStatement.executeBatch() via 'continueBatchOnError' property
+ (defaults to 'true').
+
+ - Check for connection closed in more Connection methods
+ (createStatement, prepareStatement, setTransactionIsolation,
+ setAutoCommit).
+
+ - More robust implementation of updatable result sets. Checks that
+ _all_ primary keys of the table have been selected.
+
+ - 'LOAD DATA LOCAL INFILE ...' now works, if your server is configured
+ to allow it. Can be turned off with the 'allowLoadLocalInfile'
+ property (see the README).
+
+ - Substitute '?' for unknown character conversions in single-byte
+ character sets instead of '\0'.
+
+ - NamedPipeSocketFactory now works (only intended for Windows), see
+ README for instructions.
+
+11-08-02 - Version 3.0.2-dev
+
+ - Fixed issue with updatable result sets and PreparedStatements not
+ working
+
+ - Fixed ResultSet.setFetchDirection(FETCH_UNKNOWN)
+
+ - Fixed issue when calling Statement.setFetchSize() when using
+ arbitrary values
+
+ - Fixed incorrect conversion in ResultSet.getLong()
+
+ - Implemented ResultSet.updateBlob().
+
+ - Removed duplicate code from UpdatableResultSet (it can be inherited
+ from ResultSet, the extra code for each method to handle updatability
+ I thought might someday be necessary has not been needed).
+
+ - Fixed "UnsupportedEncodingException" thrown when "forcing" a
+ character encoding via properties.
+
+ - Fixed various non-ASCII character encoding issues.
+
+ - Added driver property 'useHostsInPrivileges'. Defaults to true.
+ Affects whether or not '@hostname' will be used in
+ DBMD.getColumn/TablePrivileges.
+
+ - All DBMD result set columns describing schemas now return NULL
+ to be more compliant with the behavior of other JDBC drivers
+ for other databases (MySQL does not support schemas).
+
+ - Added SSL support. See README for information on how to use it.
+
+ - Properly restore connection properties when autoReconnecting
+ or failing-over, including autoCommit state, and isolation level.
+
+ - Use 'SHOW CREATE TABLE' when possible for determining foreign key
+ information for DatabaseMetaData...also allows cascade options for
+ DELETE information to be returned
+
+ - Escape 0x5c character in strings for the SJIS charset.
+
+ - Fixed start position off-by-1 error in Clob.getSubString()
+
+ - Implemented Clob.truncate()
+
+ - Implemented Clob.setString()
+
+ - Implemented Clob.setAsciiStream()
+
+ - Implemented Clob.setCharacterStream()
+
+ - Added com.mysql.jdbc.MiniAdmin class, which allows you to send
+ 'shutdown' command to MySQL server...Intended to be used when 'embedding'
+ Java and MySQL server together in an end-user application.
+
+ - Added 'connectTimeout' parameter that allows users of JDK-1.4 and newer
+ to specify a maxium time to wait to establish a connection.
+
+ - Failover and autoReconnect only work when the connection is in a
+ autoCommit(false) state, in order to stay transaction safe
+
+ - Added 'queriesBeforeRetryMaster' property that specifies how many
+ queries to issue when failed over before attempting to reconnect
+ to the master (defaults to 50)
+
+ - Fixed DBMD.supportsResultSetConcurrency() so that it returns true
+ for ResultSet.TYPE_SCROLL_INSENSITIVE and ResultSet.CONCUR_READ_ONLY or
+ ResultSet.CONCUR_UPDATABLE
+
+ - Fixed ResultSet.isLast() for empty result sets (should return false).
+
+ - PreparedStatement now honors stream lengths in setBinary/Ascii/Character
+ Stream() unless you set the connection property
+ 'useStreamLengthsInPrepStmts' to 'false'.
+
+ - Removed some not-needed temporary object creation by using Strings
+ smarter in EscapeProcessor, Connection and DatabaseMetaData classes.
+
+09-21-02 - Version 3.0.1-dev
+
+ - Fixed ResultSet.getRow() off-by-one bug.
+
+ - Fixed RowDataStatic.getAt() off-by-one bug.
+
+ - Added limited Clob functionality (ResultSet.getClob(),
+ PreparedStatemtent.setClob(),
+ PreparedStatement.setObject(Clob).
+
+ - Added socketTimeout parameter to URL.
+
+ - Connection.isClosed() no longer "pings" the server.
+
+ - Connection.close() issues rollback() when getAutoCommit() == false
+
+ - Added "paranoid" parameter...sanitizes error messages removing
+ "sensitive" information from them (i.e. hostnames, ports,
+ usernames, etc.), as well as clearing "sensitive" data structures
+ when possible.
+
+ - Fixed ResultSetMetaData.isSigned() for TINYINT and BIGINT.
+
+ - Charsets now automatically detected. Optimized code for single-byte
+ character set conversion.
+
+ - Implemented ResultSet.getCharacterStream()
+
+ - Added "LOCAL TEMPORARY" to table types in DatabaseMetaData.getTableTypes()
+
+ - Massive code clean-up to follow Java coding conventions (the time had come)
+
+
+07-31-02 - Version 3.0.0-dev
+
+ - !!! LICENSE CHANGE !!! The driver is now GPL. If you need
+ non-GPL licenses, please contact me <mark@mysql.com>
+
+ - JDBC-3.0 functionality including
+ Statement/PreparedStatement.getGeneratedKeys() and
+ ResultSet.getURL()
+
+ - Performance enchancements - driver is now 50-100% faster
+ in most situations, and creates fewer temporary objects
+
+ - Repackaging...new driver name is "com.mysql.jdbc.Driver",
+ old name still works, though (the driver is now provided
+ by MySQL-AB)
+
+ - Better checking for closed connections in Statement
+ and PreparedStatement.
+
+ - Support for streaming (row-by-row) result sets (see README)
+ Thanks to Doron.
+
+ - Support for large packets (new addition to MySQL-4.0 protocol),
+ see README for more information.
+
+ - JDBC Compliance -- Passes all tests besides stored procedure tests
+
+
+ - Fix and sort primary key names in DBMetaData (SF bugs 582086 and 582086)
+
+ - Float types now reported as java.sql.Types.FLOAT (SF bug 579573)
+
+ - ResultSet.getTimestamp() now works for DATE types (SF bug 559134)
+
+ - ResultSet.getDate/Time/Timestamp now recognizes all forms of invalid
+ values that have been set to all zeroes by MySQL (SF bug 586058)
+
+ - Testsuite now uses Junit (which you can get from www.junit.org)
+
+ - The driver now only works with JDK-1.2 or newer.
+
+ - Added multi-host failover support (see README)
+
+ - General source-code cleanup.
+
+ - Overall speed improvements via controlling transient object
+ creation in MysqlIO class when reading packets
+
+ - Performance improvements in string handling and field
+ metadata creation (lazily instantiated) contributed by
+ Alex Twisleton-Wykeham-Fiennes
+
+
+05-16-02 - Version 2.0.14
+
+ - More code cleanup
+
+ - PreparedStatement now releases resources on .close() (SF bug 553268)
+
+ - Quoted identifiers not used if server version does not support them. Also,
+ if server started with --ansi or --sql-mode=ANSI_QUOTES then '"' will be
+ used as an identifier quote, otherwise '`' will be used.
+
+ - ResultSet.getDouble() now uses code built into JDK to be more precise (but slower)
+
+ - LogicalHandle.isClosed() calls through to physical connection
+
+ - Added SQL profiling (to STDERR). Set "profileSql=true" in your JDBC url.
+ See README for more information.
+
+ - Fixed typo for relaxAutoCommit parameter.
+
+04-24-02 - Version 2.0.13
+
+ - More code cleanup.
+
+ - Fixed unicode chars being read incorrectly (SF bug 541088)
+
+ - Faster blob escaping for PrepStmt
+
+ - Added set/getPortNumber() to DataSource(s) (SF bug 548167)
+
+ - Added setURL() to MySQLXADataSource (SF bug 546019)
+
+ - PreparedStatement.toString() fixed (SF bug 534026)
+
+ - ResultSetMetaData.getColumnClassName() now implemented
+
+ - Rudimentary version of Statement.getGeneratedKeys() from JDBC-3.0
+ now implemented (you need to be using JDK-1.4 for this to work, I
+ believe)
+
+ - DBMetaData.getIndexInfo() - bad PAGES fixed (SF BUG 542201)
+
+04-07-02 - Version 2.0.12
+
+ - General code cleanup.
+
+ - Added getIdleFor() method to Connection and MysqlLogicalHandle.
+
+ - Relaxed synchronization in all classes, should fix 520615 and 520393.
+
+ - Added getTable/ColumnPrivileges() to DBMD (fixes 484502).
+
+ - Added new types to getTypeInfo(), fixed existing types thanks to
+ Al Davis and Kid Kalanon.
+
+ - Added support for BIT types (51870) to PreparedStatement.
+
+ - Fixed getRow() bug (527165) in ResultSet
+
+ - Fixes for ResultSet updatability in PreparedStatement.
+ - Fixed timezone off by 1-hour bug in PreparedStatement (538286, 528785).
+
+ - ResultSet: Fixed updatability (values being set to null
+ if not updated).
+
+ - DataSources - fixed setUrl bug (511614, 525565),
+ wrong datasource class name (532816, 528767)
+
+ - Added identifier quoting to all DatabaseMetaData methods
+ that need them (should fix 518108)
+
+ - Added support for YEAR type (533556)
+
+ - ResultSet.insertRow() should now detect auto_increment fields
+ in most cases and use that value in the new row. This detection
+ will not work in multi-valued keys, however, due to the fact that
+ the MySQL protocol does not return this information.
+
+ - ResultSet.refreshRow() implemented.
+
+ - Fixed testsuite.Traversal afterLast() bug, thanks to Igor Lastric.
+
+01-27-02 - Version 2.0.11
+
+ - Fixed missing DELETE_RULE value in
+ DBMD.getImported/ExportedKeys() and getCrossReference().
+
+ - Full synchronization of Statement.java.
+
+ - More changes to fix "Unexpected end of input stream"
+ errors when reading BLOBs. This should be the last fix.
+
+01-24-02 - Version 2.0.10
+
+ - Fixed spurious "Unexpected end of input stream" errors in
+ MysqlIO (bug 507456).
+
+ - Fixed null-pointer-exceptions when using
+ MysqlConnectionPoolDataSource with Websphere 4 (bug 505839).
+
+01-13-02 - Version 2.0.9
+
+ - Ant build was corrupting included jar files, fixed
+ (bug 487669).
+
+ - Fixed extra memory allocation in MysqlIO.readPacket()
+ (bug 488663).
+
+ - Implementation of DatabaseMetaData.getExported/ImportedKeys() and
+ getCrossReference().
+
+ - Full synchronization on methods modifying instance and class-shared
+ references, driver should be entirely thread-safe now (please
+ let me know if you have problems)
+
+ - DataSource implementations moved to org.gjt.mm.mysql.jdbc2.optional
+ package, and (initial) implementations of PooledConnectionDataSource
+ and XADataSource are in place (thanks to Todd Wolff for the
+ implementation and testing of PooledConnectionDataSource with
+ IBM WebSphere 4).
+
+ - Added detection of network connection being closed when reading packets
+ (thanks to Todd Lizambri).
+
+ - Fixed quoting error with escape processor (bug 486265).
+
+ - Report batch update support through DatabaseMetaData (bug 495101).
+
+ - Fixed off-by-one-hour error in PreparedStatement.setTimestamp()
+ (bug 491577).
+
+ - Removed concatenation support from driver (the '||' operator),
+ as older versions of VisualAge seem to be the only thing that
+ use it, and it conflicts with the logical '||' operator. You will
+ need to start mysqld with the "--ansi" flag to use the '||'
+ operator as concatenation (bug 491680)
+
+ - Fixed casting bug in PreparedStatement (bug 488663).
+
+11-25-01 - Version 2.0.8
+
+ - Batch updates now supported (thanks to some inspiration
+ from Daniel Rall).
+
+ - XADataSource/ConnectionPoolDataSource code (experimental)
+
+ - PreparedStatement.setAnyNumericType() now handles positive
+ exponents correctly (adds "+" so MySQL can understand it).
+
+ - DatabaseMetaData.getPrimaryKeys() and getBestRowIdentifier()
+ are now more robust in identifying primary keys (matches
+ regardless of case or abbreviation/full spelling of Primary Key
+ in Key_type column).
+
+10-24-01 - Version 2.0.7
+
+ - PreparedStatement.setCharacterStream() now implemented
+
+ - Fixed dangling socket problem when in high availability
+ (autoReconnect=true) mode, and finalizer for Connection will
+ close any dangling sockets on GC.
+
+ - Fixed ResultSetMetaData.getPrecision() returning one
+ less than actual on newer versions of MySQL.
+
+ - ResultSet.getBlob() now returns null if column value
+ was null.
+
+ - Character sets read from database if useUnicode=true
+ and characterEncoding is not set. (thanks to
+ Dmitry Vereshchagin)
+
+ - Initial transaction isolation level read from
+ database (if avaialable) (thanks to Dmitry Vereshchagin)
+
+ - Fixed DatabaseMetaData.supportsTransactions(), and
+ supportsTransactionIsolationLevel() and getTypeInfo()
+ SQL_DATETIME_SUB and SQL_DATA_TYPE fields not being
+ readable.
+
+ - Fixed PreparedStatement generating SQL that would end
+ up with syntax errors for some queries.
+
+ - Fixed ResultSet.isAfterLast() always returning false.
+
+ - Fixed timezone issue in PreparedStatement.setTimestamp()
+ (thanks to Erik Olofsson)
+
+ - Captialize type names when "captializeTypeNames=true"
+ is passed in URL or properties (for WebObjects, thanks
+ to Anjo Krank)
+
+ - Updatable result sets now correctly handle NULL
+ values in fields.
+
+ - PreparedStatement.setDouble() now uses full-precision
+ doubles (reverting a fix made earlier to truncate them).
+
+ - PreparedStatement.setBoolean() will use 1/0 for values
+ if your MySQL Version >= 3.21.23.
+
+06-16-01 - Version 2.0.6
+
+Fixed PreparedStatement parameter checking
+
+ - Fixed case-sensitive column names in ResultSet.java
+
+06-13-01 - Version 2.0.5
+
+ - Fixed ResultSet.getBlob() ArrayIndex out-of-bounds
+
+ - Fixed ResultSetMetaData.getColumnTypeName for TEXT/BLOB
+
+ - Fixed ArrayIndexOutOfBounds when sending large BLOB queries
+ (Max size packet was not being set)
+
+ - Added ISOLATION level support to Connection.setIsolationLevel()
+
+ - Fixed NPE on PreparedStatement.executeUpdate() when all columns
+ have not been set.
+
+ - Fixed data parsing of TIMESTAMPs with 2-digit years
+
+ - Added Byte to PreparedStatement.setObject()
+
+ - ResultSet.getBoolean() now recognizes '-1' as 'true'
+
+ - ResultSet has +/-Inf/inf support
+
+ - ResultSet.insertRow() works now, even if not all columns are
+ set (they will be set to "NULL")
+
+ - DataBaseMetaData.getCrossReference() no longer ArrayIndexOOB
+
+ - getObject() on ResultSet correctly does TINYINT->Byte and
+ SMALLINT->Short
+
+12-03-00 - Version 2.0.3
+
+ - Implemented getBigDecimal() without scale component
+ for JDBC2.
+
+ - Fixed composite key problem with updateable result sets.
+
+ - Added detection of -/+INF for doubles.
+
+ - Faster ASCII string operations.
+
+ - Fixed incorrect detection of MAX_ALLOWED_PACKET, so sending
+ large blobs should work now.
+
+ - Fixed off-by-one error in java.sql.Blob implementation code.
+
+ - Added "ultraDevHack" URL parameter, set to "true" to allow
+ (broken) Macromedia UltraDev to use the driver.
+
+04-06-00 - Version 2.0.1
+
+ - Fixed RSMD.isWritable() returning wrong value.
+ Thanks to Moritz Maass.
+
+ - Cleaned up exception handling when driver connects
+
+ - Columns that are of type TEXT now return as Strings
+ when you use getObject()
+
+ - DatabaseMetaData.getPrimaryKeys() now works correctly wrt
+ to key_seq. Thanks to Brian Slesinsky.
+
+ - No escape processing is done on PreparedStatements anymore
+ per JDBC spec.
+
+ - Fixed many JDBC-2.0 traversal, positioning bugs, especially
+ wrt to empty result sets. Thanks to Ron Smits, Nick Brook,
+ Cessar Garcia and Carlos Martinez.
+
+ - Fixed some issues with updatability support in ResultSet when
+ using multiple primary keys.
+
+02-21-00 - Version 2.0pre5
+
+ - Fixed Bad Handshake problem.
+
+01-10-00 - Version 2.0pre4
+
+ - Fixes to ResultSet for insertRow() - Thanks to
+ Cesar Garcia
+
+ - Fix to Driver to recognize JDBC-2.0 by loading a JDBC-2.0
+ class, instead of relying on JDK version numbers. Thanks
+ to John Baker.
+
+ - Fixed ResultSet to return correct row numbers
+
+ - Statement.getUpdateCount() now returns rows matched,
+ instead of rows actually updated, which is more SQL-92
+ like.
+
+10-29-99
+
+ - Statement/PreparedStatement.getMoreResults() bug fixed.
+ Thanks to Noel J. Bergman.
+
+ - Added Short as a type to PreparedStatement.setObject().
+ Thanks to Jeff Crowder
+
+ - Driver now automagically configures maximum/preferred packet
+ sizes by querying server.
+
+ - Autoreconnect code uses fast ping command if server supports
+ it.
+
+ - Fixed various bugs wrt. to packet sizing when reading from
+ the server and when alloc'ing to write to the server.
+
+08-17-99 - Version 2.0pre
+
+ - Now compiles under JDK-1.2. The driver supports both JDK-1.1
+ and JDK-1.2 at the same time through a core set of classes.
+ The driver will load the appropriate interface classes at
+ runtime by figuring out which JVM version you are using.
+
+ - Fixes for result sets with all nulls in the first row.
+ (Pointed out by Tim Endres)
+
+ - Fixes to column numbers in SQLExceptions in ResultSet
+ (Thanks to Blas Rodriguez Somoza)
+
+ - The database no longer needs to specified to connect.
+ (Thanks to Christian Motschke)
+
+07-04-99 - Version 1.2b
+
+ - Better Documentation (in progress), in doc/mm.doc/book1.html
+
+ - DBMD now allows null for a column name pattern (not in
+ spec), which it changes to '%'.
+
+ - DBMD now has correct types/lengths for getXXX().
+
+ - ResultSet.getDate(), getTime(), and getTimestamp() fixes.
+ (contributed by Alan Wilken)
+
+ - EscapeProcessor now handles \{ \} and { or } inside quotes
+ correctly. (thanks to Alik for some ideas on how to fix it)
+
+ - Fixes to properties handling in Connection.
+ (contributed by Juho Tikkala)
+
+ - ResultSet.getObject() now returns null for NULL columns
+ in the table, rather than bombing out.
+ (thanks to Ben Grosman)
+
+ - ResultSet.getObject() now returns Strings for types
+ from MySQL that it doesn't know about. (Suggested by
+ Chris Perdue)
+
+ - Removed DataInput/Output streams, not needed, 1/2 number
+ of method calls per IO operation.
+
+ - Use default character encoding if one is not specified. This
+ is a work-around for broken JVMs, because according to spec,
+ EVERY JVM must support "ISO8859_1", but they don't.
+
+ - Fixed Connection to use the platform character encoding
+ instead of "ISO8859_1" if one isn't explicitly set. This
+ fixes problems people were having loading the character-
+ converter classes that didn't always exist (JVM bug).
+ (thanks to Fritz Elfert for pointing out this problem)
+
+ - Changed MysqlIO to re-use packets where possible to reduce
+ memory usage.
+
+ - Fixed escape-processor bugs pertaining to {} inside
+ quotes.
+
+04-14-99 - Version 1.2a
+
+ - Fixed character-set support for non-Javasoft JVMs
+ (thanks to many people for pointing it out)
+
+ - Fixed ResultSet.getBoolean() to recognize 'y' & 'n'
+ as well as '1' & '0' as boolean flags.
+ (thanks to Tim Pizey)
+
+ - Fixed ResultSet.getTimestamp() to give better performance.
+ (thanks to Richard Swift)
+
+ - Fixed getByte() for numeric types.
+ (thanks to Ray Bellis)
+
+ - Fixed DatabaseMetaData.getTypeInfo() for DATE type.
+ (thanks to Paul Johnston)
+
+ - Fixed EscapeProcessor for "fn" calls.
+ (thanks to Piyush Shah at locomotive.org)
+
+ - Fixed EscapeProcessor to not do extraneous work if there
+ are no escape codes.
+ (thanks to Ryan Gustafson)
+
+ - Fixed Driver to parse URLs of the form "jdbc:mysql://host:port"
+ (thanks to Richard Lobb)
+
+03-24-99 - Version 1.1i
+
+ - Fixed Timestamps for PreparedStatements
+
+ - Fixed null pointer exceptions in RSMD and RS
+
+ - Re-compiled with jikes for valid class files (thanks ms!)
+
+03-08-99 - Version 1.1h
+
+ - Fixed escape processor to deal with un-matched { and }
+ (thanks to Craig Coles)
+
+ - Fixed escape processor to create more portable (between
+ DATETIME and TIMESTAMP types) representations so that
+ it will work with BETWEEN clauses.
+ (thanks to Craig Longman)
+
+ - MysqlIO.quit() now closes the socket connection. Before,
+ after many failed connections some OS's would run out
+ of file descriptors. (thanks to Michael Brinkman)
+
+ - Fixed NullPointerException in Driver.getPropertyInfo.
+ (thanks to Dave Potts)
+
+ - Fixes to MysqlDefs to allow all *text fields to be
+ retrieved as Strings.
+ (thanks to Chris at Leverage)
+
+ - Fixed setDouble in PreparedStatement for large numbers
+ to avoid sending scientific notation to the database.
+ (thanks to J.S. Ferguson)
+
+ - Fixed getScale() and getPrecision() in RSMD.
+ (contrib'd by James Klicman)
+
+ - Fixed getObject() when field was DECIMAL or NUMERIC
+ (thanks to Bert Hobbs)
+
+ - DBMD.getTables() bombed when passed a null table-name
+ pattern. Fixed. (thanks to Richard Lobb)
+
+ - Added check for "client not authorized" errors during
+ connect. (thanks to Hannes Wallnoefer)
+
+02-19-99 - Version 1.1g
+
+ - Result set rows are now byte arrays. Blobs and Unicode
+ work bidriectonally now. The useUnicode and encoding
+ options are implemented now.
+
+ - Fixes to PreparedStatement to send binary set by
+ setXXXStream to be sent un-touched to the MySQL server.
+
+ - Fixes to getDriverPropertyInfo().
+
+12-31-98 - Version 1.1f
+
+ - Changed all ResultSet fields to Strings, this should allow
+ Unicode to work, but your JVM must be able to convert
+ between the character sets. This should also make reading
+ data from the server be a bit quicker, because there is now
+ no conversion from StringBuffer to String.
+
+ - Changed PreparedStatement.streamToString() to be more
+ efficient (code from Uwe Schaefer).
+
+ - URL parsing is more robust (throws SQL exceptions on errors
+ rather than NullPointerExceptions)
+
+ - PreparedStatement now can convert Strings to Time/Date values
+ via setObject() (code from Robert Currey).
+
+ - IO no longer hangs in Buffer.readInt(), that bug was
+ introduced in 1.1d when changing to all byte-arrays for
+ result sets. (Pointed out by Samo Login)
+
+11-03-98 - Version 1.1b
+
+ - Fixes to DatabaseMetaData to allow both IBM VA and J-Builder
+ to work. Let me know how it goes. (thanks to Jac Kersing)
+
+ - Fix to ResultSet.getBoolean() for NULL strings
+ (thanks to Barry Lagerweij)
+
+ - Beginning of code cleanup, and formatting. Getting ready
+ to branch this off to a parallel JDBC-2.0 source tree.
+
+ - Added "final" modifier to critical sections in MysqlIO and
+ Buffer to allow compiler to inline methods for speed.
+
+9-29-98
+
+ - If object references passed to setXXX() in PreparedStatement are
+ null, setNull() is automatically called for you. (Thanks for the
+ suggestion goes to Erik Ostrom)
+
+ - setObject() in PreparedStatement will now attempt to write a
+ serialized representation of the object to the database for
+ objects of Types.OTHER and objects of unknown type.
+
+ - Util now has a static method readObject() which given a ResultSet
+ and a column index will re-instantiate an object serialized in
+ the above manner.
+
+9-02-98 - Vesion 1.1
+
+ - Got rid of "ugly hack" in MysqlIO.nextRow(). Rather than
+ catch an exception, Buffer.isLastDataPacket() was fixed.
+
+ - Connection.getCatalog() and Connection.setCatalog()
+ should work now.
+
+ - Statement.setMaxRows() works, as well as setting
+ by property maxRows. Statement.setMaxRows() overrides
+ maxRows set via properties or url parameters.
+
+ - Automatic re-connection is available. Because it has
+ to "ping" the database before each query, it is
+ turned off by default. To use it, pass in "autoReconnect=true"
+ in the connection URL. You may also change the number of
+ reconnect tries, and the initial timeout value via
+ "maxReconnects=n" (default 3) and "initialTimeout=n"
+ (seconds, default 2) parameters. The timeout is an
+ exponential backoff type of timeout, e.g. if you have initial
+ timeout of 2 seconds, and maxReconnects of 3, then the driver
+ will timeout 2 seconds, 4 seconds, then 16 seconds between each
+ re-connection attempt.
+
+8-24-98 - Version 1.0
+
+ - Fixed handling of blob data in Buffer.java
+
+ - Fixed bug with authentication packet being
+ sized too small.
+
+ - The JDBC Driver is now under the LPGL
+
+8-14-98 -
+
+ - Fixed Buffer.readLenString() to correctly
+ read data for BLOBS.
+
+ - Fixed PreparedStatement.stringToStream to
+ correctly read data for BLOBS.
+
+ - Fixed PreparedStatement.setDate() to not
+ add a day.
+ (above fixes thanks to Vincent Partington)
+
+ - Added URL parameter parsing (?user=... etc).
+
+
+8-04-98 - Version 0.9d
+
+ - Big news! New package name. Tim Endres from ICE
+ Engineering is starting a new source tree for
+ GNU GPL'd Java software. He's graciously given
+ me the org.gjt.mm package directory to use, so now
+ the driver is in the org.gjt.mm.mysql package scheme.
+ I'm "legal" now. Look for more information on Tim's
+ project soon.
+
+ - Now using dynamically sized packets to reduce
+ memory usage when sending commands to the DB.
+
+ - Small fixes to getTypeInfo() for parameters, etc.
+
+ - DatabaseMetaData is now fully implemented. Let me
+ know if these drivers work with the various IDEs
+ out there. I've heard that they're working with
+ JBuilder right now.
+
+ - Added JavaDoc documentation to the package.
+
+ - Package now available in .zip or .tar.gz.
+
+7-28-98 - Version 0.9
+
+ - Implemented getTypeInfo().
+ Connection.rollback() now throws an SQLException
+ per the JDBC spec.
+
+ - Added PreparedStatement that supports all JDBC API
+ methods for PreparedStatement including InputStreams.
+ Please check this out and let me know if anything is
+ broken.
+
+ - Fixed a bug in ResultSet that would break some
+ queries that only returned 1 row.
+
+ - Fixed bugs in DatabaseMetaData.getTables(),
+ DatabaseMetaData.getColumns() and
+ DatabaseMetaData.getCatalogs().
+
+ - Added functionality to Statement that allows
+ executeUpdate() to store values for IDs that are
+ automatically generated for AUTO_INCREMENT fields.
+ Basically, after an executeUpdate(), look at the
+ SQLWarnings for warnings like "LAST_INSERTED_ID =
+ 'some number', COMMAND = 'your SQL query'".
+
+ If you are using AUTO_INCREMENT fields in your
+ tables and are executing a lot of executeUpdate()s
+ on one Statement, be sure to clearWarnings() every
+ so often to save memory.
+
+7-06-98 - Version 0.8
+
+ - Split MysqlIO and Buffer to separate classes. Some
+ ClassLoaders gave an IllegalAccess error for some
+ fields in those two classes. Now mm.mysql works in
+ applets and all classloaders.
+
+ Thanks to Joe Ennis <jce@mail.boone.com> for pointing
+ out the problem and working on a fix with me.
+
+7-01-98 - Version 0.7
+
+ - Fixed DatabaseMetadata problems in getColumns() and
+ bug in switch statement in the Field constructor.
+
+ Thanks to Costin Manolache <costin@tdiinc.com> for
+ pointing these out.
+
+5-21-98 - Version 0.6
+
+ - Incorporated efficiency changes from
+ Richard Swift <Richard.Swift@kanatek.ca> in
+ MysqlIO.java and ResultSet.java
+
+ - We're now 15% faster than gwe's driver.
+
+ - Started working on DatabaseMetaData.
+
+ The following methods are implemented:
+ * getTables()
+ * getTableTypes()
+ * getColumns
+ * getCatalogs()
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/COPYING b/plugins/org.eclipse.net4j.db.mysql/lib/COPYING
new file mode 100644
index 0000000..025ed9e
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/COPYING
@@ -0,0 +1,343 @@
+GNU General Public License
+**************************
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+ freedom to share and change it. By contrast, the GNU General Public
+ License is intended to guarantee your freedom to share and change free
+ software--to make sure the software is free for all its users. This
+ General Public License applies to most of the Free Software
+ Foundation's software and to any other program whose authors commit to
+ using it. (Some other Free Software Foundation software is covered by
+ the GNU Library General Public License instead.) You can apply it to
+ your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+ price. Our General Public Licenses are designed to make sure that you
+ have the freedom to distribute copies of free software (and charge for
+ this service if you wish), that you receive source code or can get it
+ if you want it, that you can change the software or use pieces of it
+ in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+ anyone to deny you these rights or to ask you to surrender the rights.
+ These restrictions translate to certain responsibilities for you if you
+ distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+ gratis or for a fee, you must give the recipients all the rights that
+ you have. You must make sure that they, too, receive or can get the
+ source code. And you must show them these terms so they know their
+ rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+ (2) offer you this license which gives you legal permission to copy,
+ distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+ that everyone understands that there is no warranty for this free
+ software. If the software is modified by someone else and passed on, we
+ want its recipients to know that what they have is not the original, so
+ that any problems introduced by others will not reflect on the original
+ authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+ patents. We wish to avoid the danger that redistributors of a free
+ program will individually obtain patent licenses, in effect making the
+ program proprietary. To prevent this, we have made it clear that any
+ patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+ modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+ a notice placed by the copyright holder saying it may be distributed
+ under the terms of this General Public License. The "Program", below,
+ refers to any such program or work, and a "work based on the Program"
+ means either the Program or any derivative work under copyright law:
+ that is to say, a work containing the Program or a portion of it,
+ either verbatim or with modifications and/or translated into another
+ language. (Hereinafter, translation is included without limitation in
+ the term "modification".) Each licensee is addressed as "you".
+
+ Activities other than copying, distribution and modification are not
+ covered by this License; they are outside its scope. The act of
+ running the Program is not restricted, and the output from the Program
+ is covered only if its contents constitute a work based on the
+ Program (independent of having been made by running the Program).
+ Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+ source code as you receive it, in any medium, provided that you
+ conspicuously and appropriately publish on each copy an appropriate
+ copyright notice and disclaimer of warranty; keep intact all the
+ notices that refer to this License and to the absence of any warranty;
+ and give any other recipients of the Program a copy of this License
+ along with the Program.
+
+ You may charge a fee for the physical act of transferring a copy, and
+ you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+ of it, thus forming a work based on the Program, and copy and
+ distribute such modifications or work under the terms of Section 1
+ above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+ These requirements apply to the modified work as a whole. If
+ identifiable sections of that work are not derived from the Program,
+ and can be reasonably considered independent and separate works in
+ themselves, then this License, and its terms, do not apply to those
+ sections when you distribute them as separate works. But when you
+ distribute the same sections as part of a whole which is a work based
+ on the Program, the distribution of the whole must be on the terms of
+ this License, whose permissions for other licensees extend to the
+ entire whole, and thus to each and every part regardless of who wrote it.
+
+ Thus, it is not the intent of this section to claim rights or contest
+ your rights to work written entirely by you; rather, the intent is to
+ exercise the right to control the distribution of derivative or
+ collective works based on the Program.
+
+ In addition, mere aggregation of another work not based on the Program
+ with the Program (or with a work based on the Program) on a volume of
+ a storage or distribution medium does not bring the other work under
+ the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+ under Section 2) in object code or executable form under the terms of
+ Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+ The source code for a work means the preferred form of the work for
+ making modifications to it. For an executable work, complete source
+ code means all the source code for all modules it contains, plus any
+ associated interface definition files, plus the scripts used to
+ control compilation and installation of the executable. However, as a
+ special exception, the source code distributed need not include
+ anything that is normally distributed (in either source or binary
+ form) with the major components (compiler, kernel, and so on) of the
+ operating system on which the executable runs, unless that component
+ itself accompanies the executable.
+
+ If distribution of executable or object code is made by offering
+ access to copy from a designated place, then offering equivalent
+ access to copy the source code from the same place counts as
+ distribution of the source code, even though third parties are not
+ compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+ except as expressly provided under this License. Any attempt
+ otherwise to copy, modify, sublicense or distribute the Program is
+ void, and will automatically terminate your rights under this License.
+ However, parties who have received copies, or rights, from you under
+ this License will not have their licenses terminated so long as such
+ parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+ signed it. However, nothing else grants you permission to modify or
+ distribute the Program or its derivative works. These actions are
+ prohibited by law if you do not accept this License. Therefore, by
+ modifying or distributing the Program (or any work based on the
+ Program), you indicate your acceptance of this License to do so, and
+ all its terms and conditions for copying, distributing or modifying
+ the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+ Program), the recipient automatically receives a license from the
+ original licensor to copy, distribute or modify the Program subject to
+ these terms and conditions. You may not impose any further
+ restrictions on the recipients' exercise of the rights granted herein.
+ You are not responsible for enforcing compliance by third parties to
+ this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+ infringement or for any other reason (not limited to patent issues),
+ conditions are imposed on you (whether by court order, agreement or
+ otherwise) that contradict the conditions of this License, they do not
+ excuse you from the conditions of this License. If you cannot
+ distribute so as to satisfy simultaneously your obligations under this
+ License and any other pertinent obligations, then as a consequence you
+ may not distribute the Program at all. For example, if a patent
+ license would not permit royalty-free redistribution of the Program by
+ all those who receive copies directly or indirectly through you, then
+ the only way you could satisfy both it and this License would be to
+ refrain entirely from distribution of the Program.
+
+ If any portion of this section is held invalid or unenforceable under
+ any particular circumstance, the balance of the section is intended to
+ apply and the section as a whole is intended to apply in other
+ circumstances.
+
+ It is not the purpose of this section to induce you to infringe any
+ patents or other property right claims or to contest validity of any
+ such claims; this section has the sole purpose of protecting the
+ integrity of the free software distribution system, which is
+ implemented by public license practices. Many people have made
+ generous contributions to the wide range of software distributed
+ through that system in reliance on consistent application of that
+ system; it is up to the author/donor to decide if he or she is willing
+ to distribute software through any other system and a licensee cannot
+ impose that choice.
+
+ This section is intended to make thoroughly clear what is believed to
+ be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+ certain countries either by patents or by copyrighted interfaces, the
+ original copyright holder who places the Program under this License
+ may add an explicit geographical distribution limitation excluding
+ those countries, so that distribution is permitted only in or among
+ countries not thus excluded. In such case, this License incorporates
+ the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+ of the General Public License from time to time. Such new versions will
+ be similar in spirit to the present version, but may differ in detail to
+ address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the Program
+ specifies a version number of this License which applies to it and "any
+ later version", you have the option of following the terms and conditions
+ either of that version or of any later version published by the Free
+ Software Foundation. If the Program does not specify a version number of
+ this License, you may choose any version ever published by the Free Software
+ Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+ programs whose distribution conditions are different, write to the author
+ to ask for permission. For software which is copyrighted by the Free
+ Software Foundation, write to the Free Software Foundation; we sometimes
+ make exceptions for this. Our decision will be guided by the two goals
+ of preserving the free status of all derivatives of our free software and
+ of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+ FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+ OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+ PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+ OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+ TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+ PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+ REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+ WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+ REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+ INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+ OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+ TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+ POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+ possible use to the public, the best way to achieve this is to make it
+ free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+ to attach them to the start of each source file to most effectively
+ convey the exclusion of warranty; and each file should have at least
+ the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+ Also add information on how to contact you by electronic and paper mail.
+
+ If the program is interactive, make it output a short notice like this
+ when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+ The hypothetical commands `show w' and `show c' should show the appropriate
+ parts of the General Public License. Of course, the commands you use may
+ be called something other than `show w' and `show c'; they could even be
+ mouse-clicks or menu items--whatever suits your program.
+
+ You should also get your employer (if you work as a programmer) or your
+ school, if any, to sign a "copyright disclaimer" for the program, if
+ necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+ This General Public License does not permit incorporating your program into
+ proprietary programs. If your program is a subroutine library, you may
+ consider it more useful to permit linking proprietary applications with the
+ library. If this is what you want to do, use the GNU Library General
+ Public License instead of this License.
+
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/EXCEPTIONS-CONNECTOR-J b/plugins/org.eclipse.net4j.db.mysql/lib/EXCEPTIONS-CONNECTOR-J
new file mode 100644
index 0000000..7449551
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/EXCEPTIONS-CONNECTOR-J
@@ -0,0 +1,119 @@
+MySQL FLOSS License Exception
+
+The MySQL AB Exception for Free/Libre and Open Source
+Software-only Applications Using MySQL Client Libraries (the
+"FLOSS Exception").
+
+Version 0.6, 7 March 2007
+
+Exception Intent
+
+We want specified Free/Libre and Open Source Software (``FLOSS'')
+applications to be able to use specified GPL-licensed MySQL client
+libraries (the ``Program'') despite the fact that not all FLOSS
+licenses are compatible with version 2 of the GNU General Public
+License (the ``GPL'').
+
+Legal Terms and Conditions
+
+As a special exception to the terms and conditions of version 2.0
+of the GPL:
+
+ 1. You are free to distribute a Derivative Work that is formed
+ entirely from the Program and one or more works (each, a
+ "FLOSS Work") licensed under one or more of the licenses
+ listed below in section 1, as long as:
+ a. You obey the GPL in all respects for the Program and the
+ Derivative Work, except for identifiable sections of the
+ Derivative Work which are not derived from the Program,
+ and which can reasonably be considered independent and
+ separate works in themselves,
+ b. all identifiable sections of the Derivative Work which
+ are not derived from the Program, and which can
+ reasonably be considered independent and separate works
+ in themselves,
+ i. are distributed subject to one of the FLOSS licenses
+ listed below, and
+ ii. the object code or executable form of those sections
+ are accompanied by the complete corresponding
+ machine-readable source code for those sections on
+ the same medium and under the same FLOSS license as
+ the corresponding object code or executable forms of
+ those sections, and
+ c. any works which are aggregated with the Program or with a
+ Derivative Work on a volume of a storage or distribution
+ medium in accordance with the GPL, can reasonably be
+ considered independent and separate works in themselves
+ which are not derivatives of either the Program, a
+ Derivative Work or a FLOSS Work.
+ If the above conditions are not met, then the Program may only
+ be copied, modified, distributed or used under the terms and
+ conditions of the GPL or another valid licensing option from
+ MySQL AB.
+
+ 2. FLOSS License List
+
+License name Version(s)/Copyright Date
+Academic Free License 2.0
+Apache Software License 1.0/1.1/2.0
+Apple Public Source License 2.0
+Artistic license From Perl 5.8.0
+BSD license "July 22 1999"
+Common Development and Distribution License (CDDL) 1.0
+Common Public License 1.0
+Eclipse Public License 1.0
+GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
+Jabber Open Source License 1.0
+MIT license (As listed in file MIT-License.txt) ---
+Mozilla Public License (MPL) 1.0/1.1
+Open Software License 2.0
+OpenSSL license (with original SSLeay license) "2003" ("1998")
+PHP License 3.0
+Python license (CNRI Python License) ---
+Python Software Foundation License 2.1.1
+Sleepycat License "1999"
+University of Illinois/NCSA Open Source License ---
+W3C License "2001"
+X11 License "2001"
+Zlib/libpng License ---
+Zope Public License 2.0
+
+ Due to the many variants of some of the above licenses, we
+ require that any version follow the 2003 version of the Free
+ Software Foundation's Free Software Definition
+ (http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
+ the Open Source Definition by the Open Source Initiative
+ (http://www.opensource.org/docs/definition.php).
+
+ 3. Definitions
+
+ a. Terms used, but not defined, herein shall have the
+ meaning provided in the GPL.
+ b. Derivative Work means a derivative work under copyright
+ law.
+
+ 4. Applicability: This FLOSS Exception applies to all Programs
+ that contain a notice placed by MySQL AB saying that the
+ Program may be distributed under the terms of this FLOSS
+ Exception. If you create or distribute a work which is a
+ Derivative Work of both the Program and any other work
+ licensed under the GPL, then this FLOSS Exception is not
+ available for that work; thus, you must remove the FLOSS
+ Exception notice from that work and comply with the GPL in all
+ respects, including by retaining all GPL notices. You may
+ choose to redistribute a copy of the Program exclusively under
+ the terms of the GPL by removing the FLOSS Exception notice
+ from that copy of the Program, provided that the copy has
+ never been modified by you or any third party.
+
+Appendix A. Qualified Libraries and Packages
+
+The following is a non-exhaustive list of libraries and packages
+which are covered by the FLOSS License Exception. Please note that
+this appendix is provided merely as an additional service to
+specific FLOSS projects wishing to simplify licensing information
+for their users. Compliance with one of the licenses noted under
+the "FLOSS license list" section remains a prerequisite.
+
+Package Name Qualifying License and Version
+Apache Portable Runtime (APR) Apache Software License 2.0 \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/README b/plugins/org.eclipse.net4j.db.mysql/lib/README
new file mode 100644
index 0000000..2612e4c
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/README
@@ -0,0 +1,45 @@
+MySQL Connector/J @MYSQL_CJ_VERSION@ (formerly MM.MySQL)
+MySQL AB's JDBC Driver for MySQL
+Copyright (c) 2003 MySQL AB
+
+CONTENTS
+
+* License
+* Documentation Location
+
+
+LICENSE
+
+MySQL Connector/J is licensed under the GPL or a commercial license
+from MySQL AB.
+
+If you have licensed this product under the GPL, please see the COPYING
+file for more information.
+
+There are special exceptions to the terms and conditions of the GPL
+as it is applied to this software. View the full text of the
+exception in file EXCEPTIONS-CONNECTOR-J in the directory of this
+software distribution.
+
+If you have licensed this product under a commercial license from
+MySQL AB, please see the file "MySQLEULA.txt" that comes with this
+distribution for the terms of the license.
+
+If you need non-GPL licenses for commercial distribution please contact
+me <mark@mysql.com> or <sales@mysql.com>.
+
+
+DOCUMENTATION LOCATION
+
+The documentation formerly contained in this file has moved into the
+'doc' directory, where it is available in HTML, PDF and plaintext
+forms.
+
+You may also find the latest copy of the documentation on the MySQL
+website at http://dev.mysql.com/doc/refman/5.0/en/connector-j.html
+
+--
+This software is OSI Certified Open Source Software.
+OSI Certified is a certification mark of the Open Source Initiative.
+
+
diff --git a/plugins/org.eclipse.net4j.db.mysql/lib/README.txt b/plugins/org.eclipse.net4j.db.mysql/lib/README.txt
new file mode 100644
index 0000000..2612e4c
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/lib/README.txt
@@ -0,0 +1,45 @@
+MySQL Connector/J @MYSQL_CJ_VERSION@ (formerly MM.MySQL)
+MySQL AB's JDBC Driver for MySQL
+Copyright (c) 2003 MySQL AB
+
+CONTENTS
+
+* License
+* Documentation Location
+
+
+LICENSE
+
+MySQL Connector/J is licensed under the GPL or a commercial license
+from MySQL AB.
+
+If you have licensed this product under the GPL, please see the COPYING
+file for more information.
+
+There are special exceptions to the terms and conditions of the GPL
+as it is applied to this software. View the full text of the
+exception in file EXCEPTIONS-CONNECTOR-J in the directory of this
+software distribution.
+
+If you have licensed this product under a commercial license from
+MySQL AB, please see the file "MySQLEULA.txt" that comes with this
+distribution for the terms of the license.
+
+If you need non-GPL licenses for commercial distribution please contact
+me <mark@mysql.com> or <sales@mysql.com>.
+
+
+DOCUMENTATION LOCATION
+
+The documentation formerly contained in this file has moved into the
+'doc' directory, where it is available in HTML, PDF and plaintext
+forms.
+
+You may also find the latest copy of the documentation on the MySQL
+website at http://dev.mysql.com/doc/refman/5.0/en/connector-j.html
+
+--
+This software is OSI Certified Open Source Software.
+OSI Certified is a certification mark of the Open Source Initiative.
+
+
diff --git a/plugins/org.eclipse.net4j.db.mysql/license.html b/plugins/org.eclipse.net4j.db.mysql/license.html
new file mode 100644
index 0000000..d7b88e9
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/license.html
@@ -0,0 +1,319 @@
+<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"><head>
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<meta name="ProgId" content="Word.Document">
+<meta name="Generator" content="Microsoft Word 9">
+<meta name="Originator" content="Microsoft Word 9">
+<link rel="File-List" href="http://www.eclipse.org/org/documents/Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml"><title>Eclipse Public License - Version 1.0</title><!--[if gte mso 9]><xml>
+ <o:DocumentProperties>
+ <o:Revision>2</o:Revision>
+ <o:TotalTime>3</o:TotalTime>
+ <o:Created>2004-03-05T23:03:00Z</o:Created>
+ <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
+ <o:Pages>4</o:Pages>
+ <o:Words>1626</o:Words>
+ <o:Characters>9270</o:Characters>
+ <o:Lines>77</o:Lines>
+ <o:Paragraphs>18</o:Paragraphs>
+ <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
+ <o:Version>9.4402</o:Version>
+ </o:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+ <w:TrackRevisions/>
+ </w:WordDocument>
+</xml><![endif]-->
+
+
+<style>
+<!--
+ /* Font Definitions */
+@font-face
+ {font-family:Tahoma;
+ panose-1:2 11 6 4 3 5 4 4 2 4;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:553679495 -2147483648 8 0 66047 0;}
+ /* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {mso-style-parent:"";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p
+ {margin-right:0in;
+ mso-margin-top-alt:auto;
+ mso-margin-bottom-alt:auto;
+ margin-left:0in;
+ mso-pagination:widow-orphan;
+ font-size:12.0pt;
+ font-family:"Times New Roman";
+ mso-fareast-font-family:"Times New Roman";}
+p.BalloonText, li.BalloonText, div.BalloonText
+ {mso-style-name:"Balloon Text";
+ margin:0in;
+ margin-bottom:.0001pt;
+ mso-pagination:widow-orphan;
+ font-size:8.0pt;
+ font-family:Tahoma;
+ mso-fareast-font-family:"Times New Roman";}
+@page Section1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.25in 1.0in 1.25in;
+ mso-header-margin:.5in;
+ mso-footer-margin:.5in;
+ mso-paper-source:0;}
+div.Section1
+ {page:Section1;}
+-->
+</style></head>
+
+<body style="" lang="EN-US">
+
+<div class="Section1">
+
+<p style="text-align: center;" align="center"><b>Eclipse Public License - v 1.0</b>
+</p>
+
+<p><span style="font-size: 10pt;">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
+THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE,
+REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
+OF THIS AGREEMENT.</span> </p>
+
+<p><b><span style="font-size: 10pt;">1. DEFINITIONS</span></b> </p>
+
+<p><span style="font-size: 10pt;">"Contribution" means:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and<br clear="left">
+b) in the case of each subsequent Contributor:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+changes to the Program, and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+additions to the Program;</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">where
+such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution 'originates' from a Contributor
+if it was added to the Program by such Contributor itself or anyone acting on
+such Contributor's behalf. Contributions do not include additions to the
+Program which: (i) are separate modules of software distributed in conjunction
+with the Program under their own license agreement, and (ii) are not derivative
+works of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Contributor" means any person or
+entity that distributes the Program.</span> </p>
+
+<p><span style="font-size: 10pt;">"Licensed Patents " mean patent
+claims licensable by a Contributor which are necessarily infringed by the use
+or sale of its Contribution alone or when combined with the Program. </span></p>
+
+<p><span style="font-size: 10pt;">"Program" means the Contributions
+distributed in accordance with this Agreement.</span> </p>
+
+<p><span style="font-size: 10pt;">"Recipient" means anyone who
+receives the Program under this Agreement, including all Contributors.</span> </p>
+
+<p><b><span style="font-size: 10pt;">2. GRANT OF RIGHTS</span></b> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+Subject to the terms of this Agreement, each Contributor hereby grants Recipient
+a non-exclusive, worldwide, royalty-free copyright license to<span style="color: red;"> </span>reproduce, prepare derivative works of, publicly
+display, publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and object code
+form.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide,<span style="color: green;"> </span>royalty-free
+patent license under Licensed Patents to make, use, sell, offer to sell, import
+and otherwise transfer the Contribution of such Contributor, if any, in source
+code and object code form. This patent license shall apply to the combination
+of the Contribution and the Program if, at the time the Contribution is added
+by the Contributor, such addition of the Contribution causes such combination
+to be covered by the Licensed Patents. The patent license shall not apply to
+any other combinations which include the Contribution. No hardware per se is
+licensed hereunder. </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">c)
+Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor
+that the Program does not infringe the patent or other intellectual property
+rights of any other entity. Each Contributor disclaims any liability to Recipient
+for claims brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the rights and
+licenses granted hereunder, each Recipient hereby assumes sole responsibility
+to secure any other intellectual property rights needed, if any. For example,
+if a third party patent license is required to allow Recipient to distribute
+the Program, it is Recipient's responsibility to acquire that license before
+distributing the Program.</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">d)
+Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in
+this Agreement. </span></p>
+
+<p><b><span style="font-size: 10pt;">3. REQUIREMENTS</span></b> </p>
+
+<p><span style="font-size: 10pt;">A Contributor may choose to distribute the
+Program in object code form under its own license agreement, provided that:</span>
+</p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it complies with the terms and conditions of this Agreement; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b)
+its license agreement:</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">i)
+effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title
+and non-infringement, and implied warranties or conditions of merchantability
+and fitness for a particular purpose; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">ii)
+effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such
+as lost profits; </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iii)
+states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and</span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">iv)
+states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a
+medium customarily used for software exchange.<span style="color: blue;"> </span></span></p>
+
+<p><span style="font-size: 10pt;">When the Program is made available in source
+code form:</span> </p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">a)
+it must be made available under this Agreement; and </span></p>
+
+<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 10pt;">b) a
+copy of this Agreement must be included with each copy of the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Contributors may not remove or alter any
+copyright notices contained within the Program. </span></p>
+
+<p><span style="font-size: 10pt;">Each Contributor must identify itself as the
+originator of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution. </span></p>
+
+<p><b><span style="font-size: 10pt;">4. COMMERCIAL DISTRIBUTION</span></b> </p>
+
+<p><span style="font-size: 10pt;">Commercial distributors of software may
+accept certain responsibilities with respect to end users, business partners
+and the like. While this license is intended to facilitate the commercial use
+of the Program, the Contributor who includes the Program in a commercial
+product offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial
+Contributor") hereby agrees to defend and indemnify every other
+Contributor ("Indemnified Contributor") against any losses, damages and
+costs (collectively "Losses") arising from claims, lawsuits and other
+legal actions brought by a third party against the Indemnified Contributor to
+the extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor
+to control, and cooperate with the Commercial Contributor in, the defense and
+any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.</span> </p>
+
+<p><span style="font-size: 10pt;">For example, a Contributor might include the
+Program in a commercial product offering, Product X. That Contributor is then a
+Commercial Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance claims and
+warranties are such Commercial Contributor's responsibility alone. Under this
+section, the Commercial Contributor would have to defend claims against the
+other Contributors related to those performance claims and warranties, and if a
+court requires any other Contributor to pay any damages as a result, the
+Commercial Contributor must pay those damages.</span> </p>
+
+<p><b><span style="font-size: 10pt;">5. NO WARRANTY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
+WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
+MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and distributing the
+Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or
+equipment, and unavailability or interruption of operations. </span></p>
+
+<p><b><span style="font-size: 10pt;">6. DISCLAIMER OF LIABILITY</span></b> </p>
+
+<p><span style="font-size: 10pt;">EXCEPT AS EXPRESSLY SET FORTH IN THIS
+AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
+THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
+
+<p><b><span style="font-size: 10pt;">7. GENERAL</span></b> </p>
+
+<p><span style="font-size: 10pt;">If any provision of this Agreement is invalid
+or unenforceable under applicable law, it shall not affect the validity or
+enforceability of the remainder of the terms of this Agreement, and without
+further action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.</span> </p>
+
+<p><span style="font-size: 10pt;">If Recipient institutes patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Program itself (excluding combinations of the Program with
+other software or hardware) infringes such Recipient's patent(s), then such
+Recipient's rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed. </span></p>
+
+<p><span style="font-size: 10pt;">All Recipient's rights under this Agreement
+shall terminate if it fails to comply with any of the material terms or
+conditions of this Agreement and does not cure such failure in a reasonable
+period of time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use and
+distribution of the Program as soon as reasonably practicable. However,
+Recipient's obligations under this Agreement and any licenses granted by
+Recipient relating to the Program shall continue and survive. </span></p>
+
+<p><span style="font-size: 10pt;">Everyone is permitted to copy and distribute
+copies of this Agreement, but in order to avoid inconsistency the Agreement is
+copyrighted and may only be modified in the following manner. The Agreement
+Steward reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement Steward has
+the right to modify this Agreement. The Eclipse Foundation is the initial
+Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version
+of the Agreement will be given a distinguishing version number. The Program
+(including Contributions) may always be distributed subject to the version of
+the Agreement under which it was received. In addition, after a new version of
+the Agreement is published, Contributor may elect to distribute the Program
+(including its Contributions) under the new version. Except as expressly stated
+in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
+the intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.</span> </p>
+
+<p><span style="font-size: 10pt;">This Agreement is governed by the laws of the
+State of New York and the intellectual property laws of the United States of
+America. No party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each party waives
+its rights to a jury trial in any resulting litigation.</span> </p>
+
+<p class="MsoNormal"><!--[if !supportEmptyParas]-->&nbsp;<!--[endif]--><o:p></o:p></p>
+
+</div>
+
+</body></html> \ No newline at end of file
diff --git a/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/MYSQLAdapter.java b/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/MYSQLAdapter.java
new file mode 100644
index 0000000..de47175
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/MYSQLAdapter.java
@@ -0,0 +1,45 @@
+/***************************************************************************
+ * Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Eike Stepper - initial API and implementation
+ **************************************************************************/
+package org.eclipse.net4j.db.internal.mysql;
+
+import org.eclipse.net4j.db.DBException;
+import org.eclipse.net4j.db.DBType;
+import org.eclipse.net4j.db.IDBField;
+import org.eclipse.net4j.internal.db.DBAdapter;
+import org.eclipse.net4j.internal.db.DBField;
+
+import org.gjt.mm.mysql.Driver;
+
+import java.sql.SQLException;
+import java.util.Arrays;
+
+/**
+ * @author Eike Stepper
+ */
+public class MYSQLAdapter extends DBAdapter
+{
+ public MYSQLAdapter()
+ {
+ super("mysql", "5.1.5");
+ }
+
+ public Driver getJDBCDriver()
+ {
+ try
+ {
+ return new Driver();
+ }
+ catch (SQLException ex)
+ {
+ throw new DBException(ex);
+ }
+ }
+}
diff --git a/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/bundle/OM.java b/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/bundle/OM.java
new file mode 100644
index 0000000..396cf30
--- /dev/null
+++ b/plugins/org.eclipse.net4j.db.mysql/src/org/eclipse/net4j/db/internal/mysql/bundle/OM.java
@@ -0,0 +1,44 @@
+/***************************************************************************
+ * Copyright (c) 2004 - 2007 Eike Stepper, Germany.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Eike Stepper - initial API and implementation
+ **************************************************************************/
+package org.eclipse.net4j.db.internal.mysql.bundle;
+
+import org.eclipse.net4j.util.om.OMBundle;
+import org.eclipse.net4j.util.om.OMPlatform;
+import org.eclipse.net4j.util.om.OSGiActivator;
+import org.eclipse.net4j.util.om.log.OMLogger;
+import org.eclipse.net4j.util.om.trace.OMTracer;
+
+/**
+ * @author Eike Stepper
+ */
+public abstract class OM
+{
+ public static final String BUNDLE_ID = "org.eclipse.net4j.db.mysql"; //$NON-NLS-1$
+
+ public static final OMBundle BUNDLE = OMPlatform.INSTANCE.bundle(BUNDLE_ID, OM.class);
+
+ public static final OMTracer DEBUG = BUNDLE.tracer("debug"); //$NON-NLS-1$
+
+ public static final OMTracer DEBUG_SQL = DEBUG.tracer("sql"); //$NON-NLS-1$
+
+ public static final OMLogger LOG = BUNDLE.logger();
+
+ /**
+ * @author Eike Stepper
+ */
+ public static final class Activator extends OSGiActivator
+ {
+ public Activator()
+ {
+ super(BUNDLE);
+ }
+ }
+}