Return-Path: X-Original-To: apmail-db-derby-commits-archive@www.apache.org Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D6142DA7 for ; Fri, 29 Apr 2011 15:01:00 +0000 (UTC) Received: (qmail 87120 invoked by uid 500); 29 Apr 2011 15:01:00 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 87090 invoked by uid 500); 29 Apr 2011 15:01:00 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 87082 invoked by uid 99); 29 Apr 2011 15:01:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2011 15:01:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2011 15:00:47 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id E0E8E2388AC8; Fri, 29 Apr 2011 15:00:24 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1097830 [3/3] - in /db/derby/site/trunk: build/site/ build/site/manuals/ build/site/papers/DerbyTut/ build/site/releases/ src/documentation/conf/ src/documentation/content/xdocs/ src/documentation/content/xdocs/manuals/ src/documentation/c... Date: Fri, 29 Apr 2011 15:00:24 -0000 To: derby-commits@db.apache.org From: rhillegas@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20110429150024.E0E8E2388AC8@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/install_software.xml URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/install_software.xml?rev=1097830&r1=1097829&r2=1097830&view=diff ============================================================================== --- db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/install_software.xml (original) +++ db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/install_software.xml Fri Apr 29 15:00:23 2011 @@ -145,20 +145,20 @@ And don't proceed until you resolve that

Download the binary Apache Derby distribution from the Derby web site at http://db.apache.org/derby/derby_downloads.html. -These tutorial instructions use version 10.7.1.1 and +These tutorial instructions use version 10.8.1.2 and assume you downloaded one of the binary distribution files listed in the table below:

- - + +
Operating SystemDownload File
Windowsdb-derby-10.7.1.1-bin.zip
UNIX, Linux, and Macdb-derby-10.7.1.1-bin.tar.gz
Windowsdb-derby-10.8.1.2-bin.zip
UNIX, Linux, and Macdb-derby-10.8.1.2-bin.tar.gz

If a more recent release is available, download that, then substitute that version number -for 10.7.1.1 in the following instructions. +for 10.8.1.2 in the following instructions.

@@ -176,20 +176,20 @@ for 10.7.1.1 in the followi

Windows (use your extraction tool e.g. WinZip -- these instructions use mks unzip): mkdir C:\Apache -copy db-derby-10.7.1.1-bin.zip C:\Apache +copy db-derby-10.8.1.2-bin.zip C:\Apache cd C:\Apache -unzip db-derby-10.7.1.1-bin.zip +unzip db-derby-10.8.1.2-bin.zip

UNIX: mkdir /opt/Apache -cp db-derby-10.7.1.1-bin.tar.gz /opt/Apache +cp db-derby-10.8.1.2-bin.tar.gz /opt/Apache cd /opt/Apache -tar xzvf db-derby-10.7.1.1-bin.tar.gz +tar xzvf db-derby-10.8.1.2-bin.tar.gz

In both cases, the software will now be extracted into a subdirectory - named db-derby-10.7.1.1-bin. + named db-derby-10.8.1.2-bin.

@@ -204,11 +204,11 @@ your system:

Windows: -C:\> set DERBY_INSTALL=C:\Apache\db-derby-10.7.1.1-bin +C:\> set DERBY_INSTALL=C:\Apache\db-derby-10.8.1.2-bin

UNIX Korn Shell: -$ export DERBY_INSTALL=/opt/Apache/db-derby-10.7.1.1-bin +$ export DERBY_INSTALL=/opt/Apache/db-derby-10.8.1.2-bin

@@ -267,7 +267,7 @@ semicolon (;) on Windows and a colon (:)

Windows: C:\> cd %DERBY_INSTALL%\bin -C:\Apache\db-derby-10.7.1.1-bin\bin> setEmbeddedCP.bat +C:\Apache\db-derby-10.8.1.2-bin\bin> setEmbeddedCP.bat

UNIX: @@ -298,13 +298,13 @@ OS architecture: x86 OS version: 5.1 Java user name: user Java user home: C:\Documents and Settings\user -Java user dir: C:\Apache\db-derby-10.7.1.1-bin\bin +Java user dir: C:\Apache\db-derby-10.8.1.2-bin\bin java.specification.name: Java Platform API Specification java.specification.version: 1.5 --------- Derby Information -------- JRE - JDBC: J2SE 5.0 - JDBC 3.0 -[C:\Apache\db-derby-10.7.1.1-bin\lib\derby.jar] 10.7.1.1 - (1040133) -[C:\Apache\db-derby-10.7.1.1-bin\lib\derbytools.jar] 10.7.1.1 - (1040133) +[C:\Apache\db-derby-10.8.1.2-bin\lib\derby.jar] 10.8.1.2 - (1095077) +[C:\Apache\db-derby-10.8.1.2-bin\lib\derbytools.jar] 10.8.1.2 - (1095077) ------------------------------------------------------ ----------------- Locale Information ----------------- Current Locale : [English/United States [en_US]] @@ -313,7 +313,7 @@ Found support for locale: [cs] . . Found support for locale: [zh_TW] - version: 10.7.1.1 - (1040133) + version: 10.8.1.2 - (1095077) ------------------------------------------------------

@@ -343,7 +343,7 @@ C:\Apache\DB-DER~1.1-B\lib\derby.jar;C:\

UNIX: $ echo $CLASSPATH -/opt/Apache/db-derby-10.7.1.1-bin/lib/derby.jar:/opt/Apache/db-derby-10.7.1.1-bin/lib/derbytools.jar: +/opt/Apache/db-derby-10.8.1.2-bin/lib/derby.jar:/opt/Apache/db-derby-10.8.1.2-bin/lib/derbytools.jar:

Modified: db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.7.1.1.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.7.1.1.html?rev=1097830&r1=1097829&r2=1097830&view=diff ============================================================================== --- db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.7.1.1.html (original) +++ db/derby/site/trunk/src/documentation/content/xdocs/releases/release-10.7.1.1.html Fri Apr 29 15:00:23 2011 @@ -22,28 +22,6 @@

Use the links below to download a distribution of Apache Derby. You should always verify the integrity of distribution files downloaded from a mirror.

-

You are currently using [preferred]. If you encounter a -problem with this mirror, then please select another. If all -mirrors are failing, there are backup mirrors at the end of the list. -See status of mirrors. -

- -
-Other mirrors: - -
- -

There are four different distributions:

  • bin distribution - contains the documentation, javadoc, and jar files for Derby.
  • @@ -51,25 +29,25 @@ Other mirrors: + + + + + + + + + + + + + + +

    There are four different distributions:

    +
      +
    • bin distribution - contains the documentation, javadoc, and jar files for Derby.
    • +
    • lib distribution - contains only the jar files for Derby.
    • +
    • lib-debug distribution - contains jar files for Derby with source line numbers.
    • +
    • src distribution - contains the Derby source tree at the point which the binaries were built.
    • +
    +

    db-derby-10.8.1.2-bin.zip [PGP] [MD 5]
    + db-derby-10.8.1.2-bin.tar.gz [PGP] [MD5]

    + +

    db-derby-10.8.1.2-lib.zip [PGP] [MD5< /a>]
    +
    db-derby-10.8.1.2-lib.tar.gz [PGP] [ MD5]

    + +

    db-derby-10.8.1.2-lib-debug.zip [PGP] [MD5]
    + db-derby-10.8.1.2-lib-debug.tar.gz [PGP] [MD5]

    + +

    db-derby-10.8.1.2-src.zip [PGP] [MD5 ]
    + db-derby-10.8.1.2-src.tar.gz [PGP] [MD5] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)

    + +

    There are two separate Eclipse plugins for Derby:

    +
      +
    • derby_core_plugin - provides the Derby jar files to other plugins in Eclipse.
    • +
    • derby_ui_doc_plugin - provides an Apache Derby Nature in Eclipse for easy database application development.
    • +
    +

    derby_core_plugin_10.8.1.zip [PGP] [MD5]
    + derby_ui_doc_plugin_1.1.3.zip [PGP] [MD5]

    +

    Please note: both plugins must be installed for full functionality. For information on installing and using + the Derby plugins for Eclipse, please see the Using the 10 Core and 1.1 UI Derby plug-ins p age.

    +

    + +Release Notes for Apache Derby 10.8.1.2

    + +
    + +

    These notes describe the difference between Apache Derby release 10.8.1.2 and the preceding release 10.7.1.1.

    + +
    + + +

    + +Overview

    + +
    + + + +

    +The most up to date information about Derby releases can be found on the +Derby download page. +

    + + + +

    +Apache Derby is a pure Java relational database engine using standard SQL and +JDBC as its APIs. More information about Derby can be found on the +Apache web site. +Derby functionality includes: +

    + + + +
      + + +
    • Embedded engine with JDBC drivers
    • + + +
    • Network Server
    • + + +
    • Network client JDBC drivers
    • + + +
    • Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)
    • + + +
    + + + +

    +Java and JDBC versions supported: +

      + + +
    • Java SE 1.4 and higher with + JDBC 2.1, 3.0, 4.0 and 4.1
    • + + +
    • Java ME CDC/Foundation Profile 1.1 with + JSR-169 JDBC Optional Package for CDC/Foundation Profile.
    • + + +
    + + +

    + + +
    + +

    + +New Features

    + +
    + + + +

    +This is a feature release. The following new features were added: +

    + + + +
      + + + +
    • + +JDBC 4.1 - Derby's JDBC drivers support the new Java 7 methods on the java.sql and javax.sql interfaces. This support works with +the pre-GA OpenJDK 7 build 131 available at http://download.java.net/jdk7/ on March 3, 2011. Derby's implementation of these interfaces may +change in a future release in the highly unlikely event that the actual GA version of these interfaces changes.
    • + + + +
    • + +Automatic calculation of index statistics - Derby automatically refreshes statistics to help it pick better query plans.
    • + + + +
    • + +Improved interrupt handling - Interrupting connection threads no longer crashes the Derby engine.
    • + + + +
    • + +MAX optimization - On indexed tables, MAX queries run faster in more cases.
    • + + + +
    • + +XML operator portability - The xmlparse and xmlserialize operators work out-of-the-box on more platforms.
    • + + + +
    + + + +
    + +

    + +Bug Fixes

    + +
    + +

    The following issues are addressed by Derby release 10.8.1.2. These issues are not addressed in the preceding 10.7.1.1 release.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Issue IdDescription
    DERBY-5192Setting up network server for management tests hangs intermittently
    DERBY-5187More accessibility fixes needed for demo pages
    DERBY-5186dblook_test_territory.java fails on AIX with ibm 1.4.2 diffing on 1 line not removed from .out
    DERBY-5185store/rollForwardRecovery.sql stuck in RAFContainer4.recoverContainerAfterInterrupt() during shutdown
    DERBY-5181Accessibility fixes needed for release notes
    DERBY-5180Accessibility fixes needed for top-level and demo pages
    DERBY-5174Failure in UpdateStatisticsTest after DERBY-5153
    DERBY-5173RAFContainer.privGetRandomAccessFile() unwraps wrong exception type
    DERBY-5171Fix uses of <alt> and <desc> elements and figure captions
    DERBY-5170Client doesn't handle double quotes in savepoint names
    DERBY-5168Wrong syntax in identifier chain returned by SynonymAliasInfo.toString()
    DERBY-5162CLOB INOUT arg set to NULL by procedure does not preserve NULL value when re-invoked
    DERBY-5161Cannot rollback after syntax error in internal statement
    DERBY-5160NullPointerException when adding column without specifying type
    DERBY-5157Incomplete quoting of SQL identifiers in AlterTableConstantAction
    DERBY-5154Tables in documentation should not have empty cells
    DERBY-5153Intermittent ASSERT FAILED Internal Error-- statistics not found in selectivityForConglomerate when running InterruptResilienceTest
    DERBY-5152Shutting down db, information that the thread received an interrupt will not be restored to thread's interrupt flag
    DERBY-5148Fixes for problems with figures in documentation
    DERBY-5143Remove unnecessary copying of the map in getTypeMap()
    DERBY-5136Simple accessibility fixes to frames HTML doc output
    DERBY-5124NPE or assert failure printed when dropping table while statistics are written out
    DERBY-5121Data corruption when executing an UPDATE trigger
    DERBY-5119testQualifiers(org.apache.derbyTesting.functionTests.tests.store.AccessTest)java.sql.SQLException: Table/View 'FOO' already exists in Schema 'APP'.
    DERBY-5117ParameterMetaDataJdbc30Test fails with "'DUMMYINT' is not recognized as a function or procedure"
    DERBY-5116SequenceTest fails with "Sequence 'MYSEQ1' already exists"
    DERBY-5115NetworkServerControlApiTest depends on implicit ordering of test cases
    DERBY-5114Assert failure in SavepointJdbc30Test.testReleaseSqlSavepointAndRollback
    DERBY-5113Intermittent failure in BlobSetMethodsTest on Java 7: Unable to set stream: 'Reached EOF prematurely; expected 1,024, got 0.'
    DERBY-5112ImportExportTest depends on implicit ordering of test cases
    DERBY-5107BasicInMemoryDbTest depends on implicit ordering of test cases
    DERBY-5106Lacking cleanup in CheckConstraintTest.testJira4282()
    DERBY-5104InterruptResilienceTest fails to remove tables in tearDown()
    DERBY-5103ProcedureInTriggerTest depends on implicit ordering of test cases
    DERBY-5102GrantRevokeDDLTest depends on implicit ordering of test cases
    DERBY-5101TruncateTableTest depends on implicit ordering of test cases
    DERBY-5100GetCurrentPropertiesTest depends on implicit ordering of test cases
    DERBY-5099PrepareStatementTest depends on ordering of test cases
    DERBY-5095Update XML operator documentation to reflect new requirements
    DERBY-5093(patch) avoid Integer allocations fetching client meta data info
    DERBY-5092(patch) avoid Boolean allocations for rowset data in client cursor
    DERBY-5089Improve tracing/logging of runtime exceptions raised in the istat thread
    DERBY-5088ShutdownException raised in istat thread during factory call
    DERBY-5087NPE in istat daemon when encountering critical exception during shutdown
    DERBY-5086Disable istat logging by default
    DERBY-5085After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
    DERBY-5082ShutdownException in ContextManager.checkInterrupt() during shutdown
    DERBY-5079DERBY-4984 caused a regression which will not allow users to drop a table if the table was involved in a trigger action rebind during ALTER TABLE DROP COLUMN
    DERBY-5078Incorrect list of compatible JRE versions in client trace
    DERBY-5076(patch) move instanceof check up above where casts occur
    DERBY-5074test failure(s) with IBM 1.4.2 in store.InterruptResilienceTest.testRAFWriteInterrupted: java.sql.SQLException: The exception 'junit.framework.AssertionFailedError: interrupt flag lost' was thrown while evaluating an expression.
    DERBY-5071(patch) use string buffers when building strings in loops
    DERBY-5070(patch) remove unused fetching of data dictionary
    DERBY-5069Since Feb 7,2011 weme 6.2 Junit tests have failed to run completely with Failed to invoke suite():java.lang.reflect.InvocationTargetException
    DERBY-5067Performance regression tests should populate tables before creating indexes
    DERBY-5063Embedded driver allows updateBytes() on BOOLEAN column
    DERBY-5062(patch) push code assignments down to where they are used - part 2
    DERBY-5060(patch) use collection apis
    DERBY-5056Incorrect statement in reference manual about memory requirement when streaming columns
    DERBY-5055(patch) add visibility to static method calls
    DERBY-5054(patch) better npe handling in exceptional case
    DERBY-5053(patch) reduce superfluous boxing histrionics
    DERBY-5052(patch) Bad name collision causes non functional method
    DERBY-5051Update the docs to include the additional information available in derby.log. This information will be useful from product supportability stand point
    DERBY-5050BrokeredConnection could call setHoldability() without using reflection
    DERBY-5047Documentation links to java.sun.com should be updated
    DERBY-5046Intermittent assert failure in AutomaticIndexStatisticsTest.testStatisticsCorrectness
    DERBY-5045Assert failures in UpdateStatisticsTest
    DERBY-5043Document the new url attribute deregister to keep the AutoloadedDriver registers in DriverManager
    DERBY-5042ResultSet.updateBoolean() on new BOOLEAN type throws exception
    DERBY-5040On Windows, cascade of errors after failed test AutomaticIndexStatisticsTest
    DERBY-5039store/updatelocksJDBC30.sql test failing in tinderbox when background update statistics are enabled.
    DERBY-5038updatelocks test failing in tinderbox when background update statistics are enabled.
    DERBY-5037Assertion failure from index-stat-thread when running AutomaticIndexStatisticsTest
    DERBY-5036(patch) fix impossible comparison due to sign extension
    DERBY-5034(patch) bad field masking makes non functional rowsInput evaluation
    DERBY-5033(patch) System.arraycopy, being native, is more performant
    DERBY-5032(patch) derived InternalXact attempts (and fails) to override a method from base
    DERBY-5029getParentLogger() won't work after the engine has been shut down once
    DERBY-5028InterruptResilienceTest passes with IBM 1.6 SR9 but creates javacore dumps
    DERBY-5024Document the behavior of interrupt handling.
    DERBY-5023Cannot find Ant libraries when building from NetBeans
    DERBY-5022(patch) override equals correctly
    DERBY-5021(patch) avoid map look ups in a loop by using entrySet
    DERBY-5020(patch) remove redundant finalizer methods
    DERBY-5019(patch) quiet the ant build with 1.8.1+
    DERBY-5018(patch) remove erroneous throws clauses on non derivable methods that don't throw
    DERBY-5017(patch) push code assignments down to where they are used
    DERBY-5015Use Arrays.fill() in client/am/ResultSet.java
    DERBY-5013(patch) remove dead allocation
    DERBY-5012(patch) bad allocation guard in ResultSet#resetUpdatedColumnsForInsert
    DERBY-5011(patch) Client driver lexer to determine statement type: fix bad attempt at incrementing a variable
    DERBY-5009(patch) RelaseNotesTransformer: make proper string replacements for forrest
    DERBY-5008(patch) fix npe in error condition
    DERBY-5005Error when fully qualifying a field from a view in an ORDER BY clause
    DERBY-5004Typo in column name "HASH_KEY_COLUMN_NUMBER" in SYSXPLAIN_SCAN_PROPS system table documentation
    DERBY-5002In case of checksum error, insure correct error reported to user.
    DERBY-5001Intermittent bug in InterruptResilienceTest
    DERBY-5000The Derby properties section in the reference manual should provide hint about where to find server specific properties.
    DERBY-4999Docs build fails under C locale
    DERBY-4997SysinfoTest version output filtering is fragile with new java versions
    DERBY-4995Docs build creates extraneous devguide directory
    DERBY-4992Release notes should specify which Java version is needed to run Derby
    DERBY-4991The derby security policy in the Admin Guide is stale.
    DERBY-4990Documentation should state a custom security policy being required to use LDAP in conjunction with network driver
    DERBY-4988ALTER TABLE DROP COLUMN should make use of information in SYSTRIGGERS to detect column used through REFERENCING clause to find trigger dependencies
    DERBY-4987BootLockTest can hang reading spawned process output
    DERBY-4986Document the new property derby.stream.error.extendedDiagSeverityLevel for thread dump and extend diagnostic information
    DERBY-4985BootLockTest can fail with ERROR XCY03: Required property 'derby.serviceProtocol' has not been set with slow configurations
    DERBY-4983failure in jdbcapi.StatementJdbc20Test:testCompletionClosure_jdbc4_1 with j9 (j2ME/CDC)
    DERBY-4982Retrying after interrupts in store pops a bug in derbyall/storeall/storeunit/T_RawStoreFactory in some cases
    DERBY-4980Replication tests lose derby.log for slave
    DERBY-4979build.properties in plugins/eclipse/org.apache.derby.ui refers to non-existent file install_plugin.html
    DERBY-4978Document the new SQLPermission required by the JDBC 4.1 Connection.abort(Executor) method
    DERBY-4974InterruptResilienceTest fails on Solaris with Sun VMs prior to 1.6
    DERBY-4973NullPointerException in updatelocks.sql encryption tests on IBM 1.6
    DERBY-4970ClassCastException from getBlob() on string parameter
    DERBY-4968Let query stop execution if an interrupt is seen, at same time as we check the query timeout
    DERBY-4967Handle interrupt received while waiting for database lock
    DERBY-4965Boolean to char conversion results in integer
    DERBY-4964Client driver fails to convert string to boolean with setObject(col, str, Types.BIT)
    DERBY-4963Revert to FileDescriptor#sync from FileChannel#force to improve interrupt resilience
    DERBY-4960Race condition in FileContainer#allocCache when reopening RAFContainer after interrupt
    DERBY-4959NPE in network server trying to return a null LOB as a procedure output arg
    DERBY-4958Wrapper types not recognized when resolving procedures with OUT arguments.
    DERBY-4951test failure in jdbc4.ResultSetTest:testJDBC4_1 with ibm 1.6 jvm
    DERBY-4950AccessControlException when running AssertFailureTest from Ant
    DERBY-4949Backward, confusing error message when you use the wrong ResultSet.getXXX() method in the client driver
    DERBY-4948Inconsistent casing of IPv4/IPv6 in admin guide
    DERBY-4947Missing/broken synchronization in BasicDependencyManager.getDependents()
    DERBY-4946Derby 10.7 DatabaseMetaData.getTypeInfo() should not return BOOLEAN for a soft upgraded database
    DERBY-4944Embedded Derby does not start when derby.jar is dynamically uploaded / added to the classpath
    DERBY-4943TRUNCATE TABLE docs should state that it doesn't work for temporary tables
    DERBY-4942Describe how to run compatibility tests from JUnit in README
    DERBY-4941Invalid example URL in German help text for dblook
    DERBY-4939Enable istat daemon and tests
    DERBY-4938Implement istat scheduling/triggering
    DERBY-4937Enable explicit mode istat daemon code for UPDATE_STATISTICS
    DERBY-4936Add core istat daemon
    DERBY-4935Add initial istat tests
    DERBY-4933Use framework helper methods to check result sets in DatabaseMetaDataTest
    DERBY-4932Move the StringColumnVTI to the public api
    DERBY-4929Engine code should not use java/shared/org/apache/derby/shared/common/error/ErrorUtil.java
    DERBY-4928Deadlock-prone synchronization in BasicDependencyManager
    DERBY-4920suites.All stuck in RAFContainer4.awaitRestoreChannel()
    DERBY-4918Minor refactoring of SPSDescriptor
    DERBY-4915test failure in OSReadOnlyTest in assertDirectoryDeleted
    DERBY-491310.3 to 10.5 upgrade fails with ava.io.StreamCorruptedException: java.lang.ClassCastException: org.apache.derby.catalog.types.OldRoutineType incompatible with org.apache.derby.iapi.types.DataTypeDescriptor
    DERBY-4912Instability in Derby2017LayerBTest
    DERBY-4910Four replication tests fail on z/OS with junit.framework.AssertionFailedError: startMaster did not succeed.
    DERBY-4907EmbeddedXADataSource with ;create=true attribute set in setDatabaseName fails with java.sql.SQLException: Database not available
    DERBY-4897Get rid of warning for customized tags in javadoc build
    DERBY-4856Add thread dump information when derby crash
    DERBY-4853log derby.properties location and derby.log location to derby.log
    DERBY-4837Prepare lang.UpdateStatisticsTest for automatic index statistics generation
    DERBY-4771Continue investigation of automatic creation/update of index statistics
    DERBY-4741Make embedded Derby work reliably in the presence of thread interrupts
    DERBY-4727Document derby.stream.error.logBootTrace=true diagnostic property
    DERBY-4713Subclasses of ScriptTestCase can not run correctly with the non-English default locale
    DERBY-4691The Reference Guide should say that SYSCOLPERMS.COLUMNS and SYSCOLUMNS.COLUMNDEFAULT are not part of Derby's public api
    DERBY-4656eclipse ui/doc plugin 1.1.2 was built with 1.6 jvm, results in "The chosen operation is not currently available" on Add Derby Nature with 1.5 jvms
    DERBY-4614JDBC metadata gives incorrect lengths for timestamps
    DERBY-4589Corrupted database prevents startup and should be automatically repaired perhaps
    DERBY-4573Reference manual is unclear about the purpose of REFERENCEDCOLUMNS in SYSTRIGGERS table.
    DERBY-4544Referencing streaming CLOBs in (some) generated column clauses fails
    DERBY-4540'AssertionFailedError' in 'store.AccessTest.testCS4595B_UniqueIndex(AccessTest.java:1729)' on SUSE Linux / IBM JIT - r9
    DERBY-3980Conflicting select then update with REPEATABLE_READ gives lock timeout instead of deadlock
    DERBY-3788Provide a zero-admin way of updating the statisitcs of an index
    DERBY-3258'Unexpected row count: expected:<0> but was:<3>' in testReleaseCompileLocks
    DERBY-3009Out of memory error when creating a very large table
    DERBY-2949AssertionFailedError in testStalePlansOnLargeTable
    DERBY-2905Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.
    DERBY-2739Use DOM interfaces to implement XML operators
    DERBY-2515Network client does not retain the INOUT parameter value change for subsequent execution
    DERBY-2354Unable to perform select query using DISTINCT on a read-only database
    DERBY-642SELECT MAX doesn't use indices optimally
    + +
    + +

    + +Issues

    + +
    + +

    Compared with the previous release (10.7.1.1), Derby release 10.8.1.2 introduces the following new features and incompatibilities. These merit your special attention.

    + + +
    + +

    + +Note for DERBY-5121

    + +
    + + + + + +

    Summary of Change

    + + +

    +In Derby 10.7.1.1, update triggers with REFERENCING clauses can corrupt data. Users are urged to +upgrade to the next release in the 10.7 family or to 10.8. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +In Derby 10.7.1.1, UPDATE triggers which use the REFERENCING clause can be confused about which columns +to pass to their triggered actions. This can silently corrupt data +manipulated by the triggered actions. +

    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +Derby 10.7.1.1 is the only release whose triggers corrupt data this +way. Upgrading to a later 10.7 release +or to 10.8 will recompile these triggers correctly. +Applications should check for data corruption if they used 10.7.1.1 to +create UPDATE triggers with the REFERENCING clause. +

    + + + + + + +

    Rationale for Change

    + + +

    +This change was made in order to fix a data corruption problem caused +by UPDATE triggers with REFERENCING clauses. +

    + + + + +
    + +
    + +

    + +Note for DERBY-4965

    + +
    + + + + + +

    Summary of Change

    + + +

    +The JDBC-level conversion from BOOLEAN to CHAR has changed. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +In previous releases of Derby, when +using PreparedStatement.setObject() +or PreparedStatement.setBoolean() to initialize a character +type parameter (CHAR, VARCHAR, etc.) with a boolean value, the +parameter would be set to the value "1" or "0" for true +or false, respectively. +

    + + + + + +

    Incompatibilities with Previous Release

    + + +

    +In this release, PreparedStatement.setObject() +and PreparedStatement.setBoolean() will convert the boolean +values true and false to the strings "true" and +"false", respectively, if the type of the parameter is one of the +character types. +

    + + + + + +

    Rationale for Change

    + + +

    +The previous behavior caused failures in a JDBC compliance test after +Derby's meta-data started reporting that the BOOLEAN data type was +supported in version 10.7.1.1. +

    + + + + + + +

    Application Changes Required

    + + +

    +If the application expects the parameter to be set to "1" or "0" +instead of "true" or "false", it must be recoded to explicitly set the +parameter to an integer value. +

    + + + +

    +For example, if an application uses setBoolean() to set a character +type parameter, it could be changed from +

    + + + +
    +ps.setBoolean(col, b);
    +
    + + + +

    +to +

    + + + +
    +ps.setInt(col, b ? 1 : 0);
    +
    + + + +

    +in order to preserve the old behavior. +

    + + + +
    + +
    + +

    + +Note for DERBY-4963

    + +
    + + + + + +

    Summary of Change

    + + +

    +Interrupt resilience may degrade the performance of writes on some platforms. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +In Derby 10.8, INSERTs and UPDATEs may run slower on platforms which +do not support write synchronization. Affected platforms include JDK +1.4.0 and JDK 1.4.1 (on all operating systems) and Java 5 (on Mac OSX and +BSD variants). +

    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +On some platforms, INSERTs and UPDATEs may run slower than they did in +previous Derby releases. Changes needed for interrupt resilience may cause extra io calls on platforms +which do not support the "rws"/"rwd" modes in the constructor for +RandomAccessFile(File,String) + + +

    + + + + + + +

    Rationale for Change

    + + +

    +Derby's log flushing logic was changed to prevent Thread interrupts +from crashing the engine. +

    + + + + + + +

    Application Changes Required

    + + +

    +Upgrade the JVM to JDK 6 or higher if your +application suffers slower INSERTs/UPDATEs after upgrading +to Derby 10.8. +

    + + + + +
    + +
    + +

    + +Note for DERBY-4939

    + +
    + + + + + +

    Summary of Change

    + + +

    +Index cardinality statistics are updated automatically. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +During query compilation, Derby now checks if the index cardinality +statistics for the tables involved in the query are out of date. If +the statistics are outdated, the query compiler will schedule a job +that updates them in a separate thread. The thread that updates the +statistics in the background may affect the performance of the user +threads. +

    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +This release of Derby may cause more threads to be running than +previous releases did. These threads may use resources also needed by +the user threads (for example, disk bandwidth, CPU or locks on system +tables) and thereby interfere with the execution in the user threads. +

    + + + + + + +

    Rationale for Change

    + + +

    +Derby's optimizer will often choose query execution plans that yield +bad performance if the index cardinality statistics are out of date. +

    + + + + + + +

    Application Changes Required

    + + +

    +If the automatic updating of index cardinality statistics causes +problems, the application can disable it by setting the database +property derby.storage.indexStats.auto=false. +

    + + + +

    +To diagnose problems with automatic updating of index statistics, the +application may set the database +property derby.storage.indexStats.log=true. When this +property is set, the thread that updates the statistics will write +messages to the Derby system log (derby.log) every time it performs a +task. +

    + + + + +
    + +
    + +

    + +Note for DERBY-4856

    + +
    + + + + + +

    Summary of Change

    + + +

    +Diagnostics for system crashes and session errors have been expanded. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +After a severe error (system crash or session error), the Derby error log will snapshot +stack traces for all threads. On IBM +JVMs these errors will produce a javacore file too. +

    + + + +

    +To obtain thread dumps and diagnostics for +less severe errors, adjust the +derby.stream.error.extendedDiagSeverityLevel property as +described in the +Setting system-wide properties +section of the Derby Developer's Guide. +Please consult the Derby documentation for explanations of +error severities and the other possible settings of +extendedDiagSeverityLevel. +

    + + + +

    +For example, to obtain this extra information while diagnosing deadlocks, set +derby.stream.error.extendedDiagSeverityLevel=30000. Then +deadlocks will dump thread stacks into the Derby +error log. +

    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +None. +

    + + + + + + +

    Rationale for Change

    + + +

    +This change gives DBAs and tech support engineers more information to +help them diagnose errors and crashes. +

    + + + + + + +

    Application Changes Required

    + + +

    +No application changes are required. To disable this +feature, simply set +the derby.stream.error.extendedDiagSeverityLevel property to +the value 50001. +

    + + + +
    + +
    + +

    + +Note for DERBY-4614

    + +
    + + + + + +

    Summary of Change

    + + +

    +JDBC metadata reports longer precision and scale for Timestamps. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +Previously, JDBC metadata calls reported that Derby Timestamps had +precision 26 and scale 6. Now the precision of Timestamps is 29 and +the scale is 9. The following metadata were corrected: +

    + + + +
      + + +
    • + +DatabaseMetaData.getTypeInfo() - The PRECISION and MINIMUM_SCALE fields were wrong.
    • + + +
    • + +DatabaseMetaData.getColumns() - The COLUMN_SIZE and DECIMAL_DIGITS fields were wrong.
    • + + +
    • + +DatabaseMetaData.getProcedureColumns() - The PRECISION and SCALE fields were wrong.
    • + + +
    • + +DatabaseMetaData.getFunctionColumns() - The PRECISION and SCALE fields were wrong.
    • + + +
    • + +ResultSetMetaData - Wrong results came back from the getColumnDisplaySize(), getPrecision(), and getScale() methods.
    • + + +
    • + +ParameterMetaData - Wrong results came back from the getPrecision() and getScale() methods.
    • + + +
    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +Applications which rely on JDBC metadata to determine the length of +Timestamps will now display longer Timestamps. +

    + + + + + +

    Rationale for Change

    + + +

    +The metadata was changed to reflect the actual precision and scale of +Derby Timestamps, which are simply instances of java.sql.Timestamp. +

    + + + + + + +

    Application Changes Required

    + + +

    +Applications, which consulted JDBC metadata in order to determine the +length of Timestamps, should be tested (and if necessary recoded) to +verify that they correctly handle the longer lengths. +

    + + + + +
    + +
    + +

    + +Note for DERBY-2905

    + +
    + + + + + +

    Summary of Change

    + + +

    +Engine shutdown now unregisters the embedded JDBC driver. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + +

    +In release 10.1, orderly engine shutdown unregistered the embedded +JDBC driver, allowing the JVM to garbage-collect the Derby +classes. Later releases (10.2 through 10.7) did not unregister the +driver. 10.8 revives the 10.1 behavior. In 10.8, orderly engine +shutdown unregisters the embedded JDBC driver. +

    + + + +

    +After the embedded driver has been unregistered, it must be +re-registered in order to obtain a new Connection to +Derby. Re-registration occurs when the application invokes the +following statement: +

    + + + +Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance(); + + + +

    +It is also possible for an application to request orderly shutdown +without unregistering the embedded driver. After such a shutdown it is not +necessary to re-register the embedded driver. To request this kind of +shutdown, the application needs to add deregister=false to +the end of the shutdown URL. For more information on this feature, +please see the section on the deregister attribute in the Derby +Reference Manual. +

    + + + + + + +

    Incompatibilities with Previous Release

    + + +

    +None. +

    + + + + + + +

    Rationale for Change

    + + +

    +The 10.1 behavior has been revived so that the JVM can +garbage-collect the Derby classes after orderly engine shutdown. +

    + + + + + + +

    Application Changes Required

    + + +

    +Applications no longer need to call +DriverManager.deregister(driver) in order to enable garbage-collection of +the Derby classes after orderly engine shutdown. +

    + + + + +
    + +
    + +

    + +Note for DERBY-2739

    + +
    + + + + + +

    Summary of Change

    + + +

    +The requirements for XML operators have changed. +

    + + + + + + +

    Symptoms Seen by Applications Affected by Change

    + + + +

    +After upgrading to Derby 10.8, applications may fail if they use the +XMLPARSE, XMLSERIALIZE, XMLQUERY, +and XMLEXISTS operators. Using those operators may raise the following error message: +

    + + + +
    +ERROR XML00: Failed to locate 'XPath 3.0' API or implementation classes.  XML operations are not permitted unless these classes are in your classpath.
    +
    + + + +

    +This happens if the classpath doesn't include +the +DOM Level 3 XPath +interfaces or an implementation of those interfaces. +

    + + + +

    Incompatibilities with Previous Release

    + + +

    +On Java 5 and earlier JVMs, the XMLPARSE, XMLSERIALIZE, XMLQUERY, +and XMLEXISTS operators may fail as described above. +

    + + + + + +

    Rationale for Change

    + + + +

    +Previous releases of Derby required a recent version of Apache +Xalan-Java in order to support the XML operators. Since not all +platforms include Apache Xalan-Java, and some platforms contain a +modified version with a different interface, these operators didn't +work out of the box on many platforms. +

    + + + +

    +In this release, the XML operators access the platform's XML libraries +via the javax.xml and org.w3c.dom interfaces instead +of accessing the Xalan implementation classes directly. This change +makes the XML operators work out of the box on most Java SE 6 or later +platforms, but may break the functionality on older platforms that +don't contain all the required interfaces. +

    + + + + + +

    Application Changes Required

    + + + +

    +In environments affected by this change, the XML operators can be fixed +by upgrading the JVM (IBM's versions 1.5.0 and +1.6.0 and Oracle's version 1.6.0 are known to work) or by installing +a recent version of Apache Xalan-Java. +

    + + + +

    +Installation of Xalan-Java may require the Endorsed Standards Override +Mechanism. This is described in the "XML data types and +operators" section of the Derby Developer's Guide. +

    + + + + +
    + +
    + +

    + +Build Environment

    + +
    + +

    Derby release 10.8.1.2 was built using the following environment:

    + +
      + +
    • + +Branch - Source code came from the 10.8 branch.
    • + +
    • + +Machine - Mac OS X 10.5.8.
    • + +
    • + +Ant - Apache Ant version 1.7.1 compiled on June 27 2008.
    • + +
    • + +JDK 1.4 - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_22-b02-329).
    • + +
    • + +Java 6 - Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125).
    • + +
    • + +Compiler - The 1.6.0_17-b04-248-9M3125 javac was used to compile all classes.
    • + +
    • + +JSR 169 - Java ME support was built using libraries from phoneME Advanced Milestone Release 2.
    • + +
    + +
    + +

    + +Verifying Releases

    + +
    + + + +

    It is essential that you verify the integrity of the downloaded +files using the PGP and MD5 signatures. MD5 verification ensures the +file was not corrupted during the download process. PGP verification +ensures that the file came from a certain person.

    + + + +

    The PGP signatures can be verified using +PGP or +GPG. +First download the Apache Derby +KEYS +as well as the asc signature file for the particular +distribution. It is important that you get these files from the ultimate +trusted source - the main ASF distribution site, rather than from a mirror. +Then verify the signatures using ...

    + + + +
    +% pgpk -a KEYS
    +% pgpv db-derby-X.Y.tar.gz.asc
    +
    +or
    +
    +% pgp -ka KEYS
    +% pgp db-derby-X.Y.tar.gz.asc
    +
    +or
    +
    +% gpg --import KEYS
    +% gpg --verify db-derby-X.Y.tar.gz.asc
    +
    +
    + + + +

    To verify the MD5 signature on the files, you need to use a program +called md5 or md5sum, which is +included in many unix distributions. It is also available as part of +GNU +Textutils. Windows users can get binary md5 programs from here, here, or +here.

    + + + +

    We strongly recommend that you verify your downloads with both PGP and MD5.

    + + + + +
    + + + + +