db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: text of release announcement for
Date Wed, 17 Apr 2013 11:34:32 GMT
Rick Hillegas <rick.hillegas@oracle.com> writes:

> Here's what I have so far. Please help me improve this. I plan to
> announce the release in the next day or two.
> Thanks,
> -Rick
> --------------------------------
> Derby contains the following new features:
> system procedure for invalidating stored prepared statements when you
> think that your metadata queries or triggers are misbehaving--for
> example if they throw a NoSuchMethodError on execution. See the
> section on this new system procedure in the Derby Reference Manual.
>     * Unencrypting databases - Encryption can be turned off on
> existing databases. See the section on the decryptDatabase attribute
> in the Derby Reference Manual.
>     * Small device profile - Derby runs on the small CP2 profile of Java 8.
>     * JDBC 4.2 - Derby supports the Java 8 enhancements to JDBC.
>     * User-defined aggregates - Applications can create their own
> aggregate operators. See the "CREATE DERBY AGGREGATE" section in the
> Derby Reference Manual.
>     * Varargs routines - SQL routines can be bound to user-written
> Java methods which have variable length argument lists.
>     * Optional tools - Derby has new, optional tools to support data
> migration and metadata queries. See the "Optional tools" section in
> the Derby Tools and Utilities Guide.
> In addition, Derby contains many bug, security, and
> documentation fixes.
> Please try out this new release.

Looks good to me.

In one of the comments on DERBY-6075 it was suggested that we added a
note about the apparent compilation speed improvements. Something along
these lines, perhaps:

   * Faster query compilation - A number of small changes have made the
     SQL compiler leaner and faster.

Maybe we could reorder the list to make it more focused. For example:

- Move JDBC 4.2 to the top of the list, since the JDBC interface is our
  primary interface, and a new version is a big thing

- Have small device profile next, as support for a new platform is also
  significant news

- Mention the new SQL features before unencrypting databases (to focus
  on new functionality before the ability to turn off existing
  functionality) and before the new procedure (to focus on functionality
  most applications could benefit from before functionality that is only
  needed in scenarios we hope won't happen; bugs that corrupt the system

Knut Anders

View raw message