Vertx Jooq Versions Save

A jOOQ-CodeGenerator to create vertx-ified DAOs and POJOs.

6.5.5

1 year ago
  • Fix Use enum literal instead of toString for datatype conversion #209
  • Update to jooq 3.17.3
  • Update to vertx 4.3.3
  • Update mutiny dependencies
  • Update rx dependencies

6.5.0

2 years ago

6.4.0

2 years ago
  • Added rxjava3 support via dedicated vertx-jooq-rx3-reactive module.
  • Added BigDecimal support.
  • Breaking change: Minimum required Java version changed from 8 to 11 (required by latest jOOQ version).
  • Bumped Vert.x version to 4.2.3
  • Bumped jOOQ version to 3.15.5

6.3.0

3 years ago
  • Added stream support for the reactive drivers. This long overdue feature allows you to process large chunks of data without running out of memory. The available methods depend on the chosen API:
  • Expose the used RowMapper in reactive QueryExecutors for convenient usage.

6.2.0

3 years ago
  • Add support for jooq 3.14 #166

6.0.0

3 years ago

Vertx 4 Support

  • Upgrade vertx to 4.0.0. A big shout out to vertx-jooq user doctorpangloss for the groundwork.
  • Enhanced PgConverter: previously, PGConverter was only considered when converting from or into a JsonObject. With the new release you can now convert anything from a io.vertx.sqlclient.Row into your user object. For that reason I've introduced the new RowConverter. For an example check out the CommaSeparatedStringIntoListConverter.
  • Added support of user-types like java.util.List<U> in your POJOs. Checkout the PostgresConfigurationProvider of how to configure it.
  • Removal of the async driver. There is actually no reason to use this driver over the reactive driver from vertx. It just adds confusion for initial users and worsens maintainability.
  • Removal of the CompletableFuture-API. When this project was started, the io.vertx.core.Future was in a bad shape. Many methods for composition and error handling were missing and made it hard to actually use. In the past couple of months this has been fixed - making the io.vertx.core.Future-API a first-class choice. In case you really need the interoperability with CompletionStage/CompletableFuture just call io.vertx.core.Future#toCompletionStage() to convert it into, or the static method Future.createFromCompletionStage to convert from a CompletionStage.

5.2.1

3 years ago

The following dependencies have been upgraded:

  • upgrade junit to 4.13.1
  • upgrade vertx to 3.9.4
  • upgrade jooq to 3.13.5 The following bug has been fixed
  • #159 fix an issue for windows users and the generated package names

Note: this will most likely be the last release depending on the vertx 3.x and jooq 3.13.x branches. As vertx will integrate first-class CompletionStage support and the io.vertx.Future-API has improved dramatically, we will most likely drop the -completablefuture modules entirely.

5.2.0

3 years ago

5.1.0

4 years ago

Noteworthy additions / changes

  • Introduction of PgConverter for the reactive modules. This gives users finally the opportunity to use custom POJOs instead of JsonObjects. The generators are also properly used in the fromJson and toJson-methods.
  • New BuildOptions when creating a code generator using VertxGeneratorBuilder. Currently one flag can be set which determines whether to use singletons (default) for converters or instantiate them every time. When set to SINGLETON-mode, this will create a class with references to all Converters and Bindings that are used.
  • Upgrade to jOOQ 3.13.1
  • BREAKING findManyBy-methods now take Collection as argument
  • Stream over QueryResult

Resolved issues

https://github.com/jklingsporn/vertx-jooq/milestone/18?closed=1