From 9051b8defe5d6ffed63accbdf74aea670cf26f4f Mon Sep 17 00:00:00 2001 From: Lukas Eder Date: Sun, 24 Jul 2011 17:06:56 +0000 Subject: [PATCH] Release 1.6.3 --- .../release/template/RELEASENOTES.txt | 81 +++++++++++++++++++ 1 file changed, 81 insertions(+) diff --git a/jOOQ-release/release/template/RELEASENOTES.txt b/jOOQ-release/release/template/RELEASENOTES.txt index e2ac57de8a..d06efd7054 100644 --- a/jOOQ-release/release/template/RELEASENOTES.txt +++ b/jOOQ-release/release/template/RELEASENOTES.txt @@ -2,6 +2,87 @@ jOOQ Release notes ------------------ For an overview, see also https://sourceforge.net/apps/trac/jooq/report/6 +Version 1.6.3 +================================================================= + +This is mainly a maintenance release with lots of bugfixes, +mostly around code generation, plain SQL tables, and data types. +Please note that generated source code may contain incompatible +changes due to #639 (see below for details)! + +Apart from that, project CURSOR is advancing and it is now +possible to unnest arrays into tables. See this article for +details about where jOOQ is heading with project CURSOR: + +http://lukaseder.wordpress.com/2011/07/24/the-power-of-ref-cursor-types/ + +Features and improvements +------------------------- +#679 - Improve H2 NVL2 support as of H2 1.3.156 +#680 - Improve H2 ROUND support as of H2 1.3.156 +#735 - Add README documentation to GitHub +#736 - Add more info regarding number of generated artefacts in + jooq-codegen logging +#750 - Add DataType.isNumeric(), .isString(), .isTemporal(), + .isBinary() +#754 - Log query as executed by JDBC PreparedStatement when + TRACE logging (without inlining variables) +#752 - CURSOR: Add support for selecting from ARRAY types +#762 - Use H2's native support of NVL, instead of COALESCE +#764 - CURSOR: Add support for selecting from ARRAY types + returned from stored functions + +API changes (backwards-incompatible) +------------------------------------ +#639 - Map DECIMAL(n, 0) and NUMBER/NUMERIC(n, 0) data types + to Byte/Short/Integer/Long/BigInteger instead of + BigDecimal in generated source code. Re-generated code + will not be compatible! + +API changes (backwards-compatible) +---------------------------------- + +API changes (previous API now deprecated) +----------------------------------------- +#731 - Inconsistent API with Field.lessOrEqualToXXX(). Removed + "To" from method name +#757 - Deprecate Factory.constant() methods + +Test cases +---------- +#731 - Add missing integration tests for equalAll(), equalSome() + and similar methods +#747 - Upgrade H2 to 1.3.158 + +Bug fixes +--------- +#632 - Sybase error : column @p0 not found in nested SELECT +#700 - Restore HSQLDB ARRAY support with INFORMATION_SCHEMA + change in HSQLDB 2.2.3, and some fixes in 2.2.5 +#725 - Cannot insert byte[] data with plain SQL +#733 - H2 changed JDBC type for ResultSet/CURSOR from 0 to -10, + like Oracle +#737 - Compilation errors in generated source code if table + fields contain spaces +#738 - Compilation errors in generated source code if MySQL + procedure parameter type contains two comma-separated + arguments (like DECIMAL(10,2)) +#739 - Postgres navigator methods and keys are not re-generated + in the same order +#740 - Formatting is broken on Result.format() with some special + newline characters +#743 - Make SQL Server INFORMATION_SCHEMA independent from + HSQLDB again, to prevent incompatibility issues +#744 - Ingres REAL and FLOAT4 types are generated as FLOAT/FLOAT8 + which maps to java.lang.Double, instead of java.lang.Float +#753 - Postgres error when binding array that contains null + values +#755 - NullPointerException when converting an array containing + a null value +#766 - Bad decoding of JDBC Types BIGINT (to BigInteger instead + of Long) and REAL (to BigDecimal instead of Float) when + plain SQL tables are involved + Version 1.6.2 =================================================================