Version 3.2.6 - July 15, 2014
================================================================================

This is a patch release with some useful fixes for the 2.6 branch

Bug fixes
---------
#2335 - SQL syntax error when projecting two columns of the same name along with
        a LIMIT clause in Oracle
#2646 - SQL Server error "The text, ntext, and image data types cannot be
        compared or sorted" when using LIMIT with a SELECT [text, image]
        statement
#2700 - DAO.insert() and other DAO operations do not respect DEFAULT values
#3186 - Bad SQL rendered for FOR UPDATE clause in Firebird
#3191 - ResultQuery.keepStatement(true) doesn't work correctly with
        DataSourceConnectionProvider
#3195 - IN predicate with subquery cannot have LIMIT .. OFFSET clause in Oracle
#3200 - Converter does not work when loading CSV files
#3226 - DefaultConnectionProvider shouldn't use DSL class for DEBUG logging
#3234 - Connection Leak With BatchCRUD operations
#3241 - Cursor.iterator() does not correctly implement Iterator.next() contract
        with respect to NoSuchElementException
#3267 - Misleading DSLContext#batch Javadoc. It should be clear that an
        additional call to execute() is needed.
#3277 - SQLite DECIMAL(p, s) types are not correctly recognised
#3282 - inputSchema / outputSchema codegen configuration has no effect in
        Oracle, if inputSchema is lower-cased
#3294 - DSLContext.renderNamedParameters() doesn't replace ?, ? by :1, :2 in
        plain SQL QueryParts
#3309 - Don't use "deploy" as Maven <defaultGoal/>
#3328 - Re-create old DefaultConfiguration constructors for backwards-
        compatibility
#3333 - maven-compiler-plugin configuration in jooq-parent pom file uses the
        deprecated compilerArguments parameter
#3342 - Cannot INSERT into tables with Firebird BLOB types
#3347 - Field.in(T...) should defend against Collection arguments
#3382 - NOT NULL constraints and type information are incorrectly generated when
        using Firebird DOMAINs for data types
#3388 - Replace SQL Server's ROW_NUMBER() OVER(ORDER BY @@version) by ORDER BY
        (SELECT 0)