Releases: jklingsporn/vertx-jooq
Releases · jklingsporn/vertx-jooq
6.5.5
6.5.0
- Add modules for mutiny-API!
- Fix Reactive QueryExecutor transaction rollback fails to close connection.
- Make
commit()androllback()return a failedFuture/Completableinstead of throwing anExceptionin case of failure
for the reactive QueryExecutors.
6.4.0
- 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
- 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:- Classic
- choose between the usage of a
Cursoror aRowStream<Row> - Cursor example
- RowStream example
- choose between the usage of a
- RX
- choose between
Flowable<Row>andFlowable<P> - Flowable example
- choose between
- Classic
- Expose the used
RowMapperin reactiveQueryExecutorsfor convenient usage.
6.2.0
6.0.0
Vertx 4 Support
- Upgrade vertx to 4.0.0. A big shout out to vertx-jooq user doctorpangloss for the
groundwork. - Enhanced
PgConverter: previously,PGConverterwas only considered when converting from or into aJsonObject. With
the new release you can now convert anything from aio.vertx.sqlclient.Rowinto your user object. For that reason I've
introduced the newRowConverter. For an example check out the
CommaSeparatedStringIntoListConverter. - Added support of user-types like
java.util.List<U>in your POJOs. Checkout thePostgresConfigurationProviderof 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, theio.vertx.core.Futurewas 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 theio.vertx.core.Future-API a first-class choice. In case you really need
the interoperability withCompletionStage/CompletableFuturejust callio.vertx.core.Future#toCompletionStage()to
convert it into, or the static method Future.createFromCompletionStage to convert from aCompletionStage.
5.2.1
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
- Add @DataObject for generated POJOs
- This nice enhancement allows you to add the
@DataObjectannotation to the generated POJOs. This is very handy when you
are working with ServiceProxies etc. - Due to the dependency to the
vertx-codegen-module this feature is disabled by default. This is how you enable it
for the classic reactive generator:VertxGeneratorBuilder.init().withClassicAPI().withPostgresReactiveDriver().build(new BuildOptions().withBuildFlags(EnumSet.of(BuildOptions.BuildFlag.GENERATE_DATA_OBJECT_ANNOTATION)))
- This nice enhancement allows you to add the
- Add limit to generated findMany-methods
- Conveniently find many POJOs limited by your choice
- Default conversion of java.util.time types
- Finally handles the
to/fromJson-conversion ofLocalDateTime,OffsetDateTime,ZonedDateTime,LocalTimeandLocalDate
- Finally handles the
- Support postgres bytea type in the reactive driver
- Upgrade to vert.x 3.9.2
- Upgrade to jOOQ 3.13.3
- Link to all resolved issues
5.1.2
5.1.0
Noteworthy additions / changes
- Introduction of
PgConverterfor the reactive modules. This gives users finally the opportunity to use custom POJOs instead ofJsonObjects. The generators are also properly used in thefromJsonandtoJson-methods. - New
BuildOptionswhen creating a code generator usingVertxGeneratorBuilder. Currently one flag can be set which determines whether to use singletons (default) for converters or instantiate them every time. When set toSINGLETON-mode, this will create a class with references to allConvertersandBindingsthat are used. - Upgrade to jOOQ 3.13.1
- BREAKING
findManyBy-methods now takeCollectionas argument - Stream over
QueryResult
Resolved issues
https://github.com/jklingsporn/vertx-jooq/milestone/18?closed=1