vertx-jooq-async the (un)beloved child of vertx-jooq has been released in version 0.4! This version finally implements
insertReturningPrimaryAsync in all
In addition, the complex code in the DAOs default methods has been abstracted and moved to
vertx-jooq-async-shared. That means less code duplication and fewer points of failure – a move that will very likely be done in vertx-jooq soon as well.
Finally the vertx-dependency version has been bumped to 3.5. (and so the support for RXJava2).
* Unfortunately, this only works for MySQL and numeric auto-increment keys. That is, because the implementation is based on the implementations of
io.vertx.ext.asyncsql.impl.AsyncSQLConnectionImpl and only the MySQL variant returns the generated ID.
Sometimes I find myself in the situation where I have to perform some asynchronous tasks and perform another asynchronous task when all those tasks have been completed. As always in such situations, I’ve searched stackoverflow for a how-to and the top rated answer suggests the following solution:
That solution totally works and it is good. However, if you often deal with
Streams, a more functional approach would be neat. So I started coding a
Collector that does this operation for me in one go. I won’t go into detail of how a
Collector works, but this blog-post helped me out a lot understanding it.
Finally I ended up with this solution, which I’ve uploaded to github:
And here is how you would use it:
Obviously it was late yesterday ^^ The solution I posted was hidden in another answer with less upvotes. It suggest using
Collectors.collectAndThen together with the sequence-method above. In my opinion this is cleaner than following my approach with writing the
Collector on your own (DRY-principle). The final solution is posted below and it contains another
Collector-factory method that can be used if you’re not interested in the results or the
CompletableFutures to collect are of type
Note: Unfortunately, the dependencies to rxjava1 haven’t been removed completely in 2.4.0. RX users please checkout version 2.4.1.
I’m happy to announce the release of vertx-jooq 2.4. The main driver behind this release was the dependency upgrade to vertx 3.5 and thus the change of the rx-dependency in vertx-jooq-rx from rxjava to rxjava2. In addition, the JSON key names of the generated POJO are now the same as their database counterparts. This change has been announced here. Last but not least, a bug has been fixed when dealing with