jOOQ 2.6.3 / 3.0.0-RC1

Developer: Website: License / Price: Platforms: Databases: Language: Last Updated: Category: Lukas Eder | More scripts www.jooq.org Apache License  Windows / Linux / Mac OS / BSD / Solaris MSSQL / MySQL / PostgreSQL / Oracle / Access / Flat file Java February 26th, 2013, 19:47 GMT [view history] C: \ Database Tools

It combines active records, stored procedures, advanced data types, complex SQL, typesafety, source code generation and Java in a fluent, intuitive DSL.

jOOQ generates a simple Java representation of the database schema.

For every table, view, stored procedure, enum, UDT is a class.

jOOQ implements an easy-to-use active record pattern. It is NOT an OR-mapper, but provides a 1:1 mapping between tables/views and classes. Between columns and members.

It also allows for writing compile-time typesafe querying using its built-in DSL.

jOOQ supports all standard SQL language features including the more complex UNION's, nested SELECTs, JOINs, aliasing

jOOQ allows developers the use of vendor-specific extensions such as stored procedures, UDT's, ARRAY's and many more.

Here are some key features of "jOOQ":

General features:
· Object Oriented SQL Modelling
· SQL code generation
· OR-Mapping
· Typesafe SQL
· Stored procedure and UDT support

Supported databases:
· MySQL 5.1.41 and 5.5.8
· H2 1.3.154
· Oracle XE 10.2.0.1.0
· DB2 9.7
· PostgreSQL 9.0
· HSQLDB 2.0.0
· SQLite with inofficial JDBC driver v056
· Derby 10.7
· MSSQL
· Sybase

Future support for:
· Ingres
· Firebird

Requirements:

· Java 1.6 or higher

What's New in This Release: [ read full changelog ]

· Bad Postgres array serialisation when " or \ characters are contained in a String[]
· Inefficient implementations of AbstractDataType.equals() and hashCode()
· Improve AbstractField.hashCode() and AbstractTable.hashCode() and similar, as these two are called very often
· Inefficient call to String.split() in StringUtils.toCamelCase() leads to non-negligible performance ovrerhead in POJO transformation calls
· Bad SQL rendered when combining ORDER BY [ some-function ] with LIMIT .. OFFSET in DB2, SQL Server
· Bad SQL rendered for OVER (ORDER BY [ some-function ]) for SQL Server and Sybase
· Thread safety issue in org.jooq.impl.FieldList
· Bad reference to org.jooq.debug.[impl].DebugListener in the manual
· Bad code generated when the same table name exists in multiple schemas in SQL Server

Via: jOOQ 2.6.3 / 3.0.0-RC1