Hi Lukas, as always thank you Lukas for this great piece of software. It is a very nice christmas gift.
I immediately recreated sources and switch to new JSR-310 API. This makes source much more readable. mery christmas Sascha On Freitag, 23. Dezember 2016 06:21:05 CET Lukas Eder wrote: > Version 3.9.0 - December 23, 2016 > ============================================================================ > ==== > > This is another very exciting release with great new features: > > Experimental Parser > ------------------- > > This is an extremely exciting strategic feature for jOOQ. jOOQ users are > used to > creating SQL statements by "manually" creating a SQL expression tree > through the > jOOQ API. But nothing should prevent us from parsing string-based (and > vendor- > specific!) SQL statements into jOOQ expression trees. In the future this > can be > used, for instance, to translate (and format) one SQL dialect into another, > making jOOQ not only an excellent SQL client API for Java, but a > general-purpose > SQL API. > > The new Parser API is available from DSLContext.parser() and is currently > deprecated as "experimental" (and incomplete). We're including it in jOOQ > 3.9 > for public review, so we're looking forward for any feedback you may have! > > Checker framework integration > ----------------------------- > > We've annotated all of our API with the @Support annotation for quite a > while. > This annotation allows for documenting what SQL clause or function is > available > in what SQLDialect (and version). If that's not enough for you, do check > out our > new JSR 308 / Checker Framework integration, which allows jOOQ API > consumers to > "type check" their API usage for a given SQL dialect. For instance, using > MySQL, > you can now get compilation errors if you're accidentally using > Oracle-specific > API. > > More info in this blog post here: > https://blog.jooq.org/2016/05/09/jsr-308-and-the-checker-framework-add-even-> > more-typesafety-to-jooq-3-9/ > > Better Oracle 12c and PL/SQL integration > ---------------------------------------- > > Oracle 12c introduced a variety of new features that we finally support in > jOOQ > as well, including the new IDENTITY column type or the OFFSET FETCH clause, > which was emulated using ROWNUM filtering, thus far. > > In addition to the above, we're continuing our extended PL/SQL support by > offering an emulation for the (de)serialisation of PL/SQL RECORD types. > This is > particularly interesting for everyone who used Oracle's now deprecated > (12cR1) > and removed (12cR2) JPublisher for PL/SQL bindings. > > More info about this here: > https://blog.jooq.org/2016/11/08/use-jooq-to-read-write-oracle-plsql-record-> > types/ > > JSR-310 Java Time API support > ----------------------------- > > We're now confident that we can support the "old" JDBC date time types and > the > "new" JSR-310 Java Time API types in parallel in a single API. With this in > place, jOOQ now includes a <javaTimeTypes/> code generator configuration, > that replaces the "old" JDBC date time types in generated code. > > The upcoming patch releases for jOOQ 3.9.x will further improve the > situation > for TIME[STAMP] WITH TIME ZONE types in databases that do support them. Your > continued feedback in this area is very welcome. > > New DDL statements and clauses > ------------------------------ > > As in every release, we've added support for tons of new DDL statements and > clauses, including: > > - A variety of RENAME statements > - The { CREATE | ALTER | DROP } SCHEMA statements > - The useful IF EXISTS clause for ALTER and DROP statements > - The useful IF NOT EXISTS clause for CREATE statements > - Support for partial indexes (CREATE INDEX .. WHERE) > - Support for ASC | DESC ordering in CREATE INDEX statements > - Support for Oracle's CONSTRAINT .. USING INDEX .. clause > - Support for IDENTITY columns > - Better support for constraint construction > > Improved transactions API > ------------------------- > > The existing transactions API creates a new "scope" for each transaction, -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part.
