Lukas Eder

> looking into this, but when I try to reproduce: Maybe this has changed already due to my recent reports in this area? I've made a few :) > Are...

This is a bigger task. We would also have to be able to bind `MULTISET` types using `val(x, t)` (including non-`NULL` values), but that just produces this exception: ``` org.jooq.exception.DataAccessException:...

This is being requested here: - https://stackoverflow.com/q/79780754/521799

Using `coerce()` also doesn't work

A more generic case is: - https://github.com/jOOQ/jOOQ/issues/19137

Interestingly, due to the implementation of `MultisetDataType.convert(null)`, which produces an empty `ResultImpl` of the `MULTISET` type, rather than a `NULL` value, we cannot actually return a `NULL` value here easily....

Fixed in versions: - 3.21.0 - 3.20.9 (https://github.com/jOOQ/jOOQ/issues/19174) - 3.19.28 (https://github.com/jOOQ/jOOQ/issues/19175) - 3.18.35 (https://github.com/jOOQ/jOOQ/issues/19176)

An additional issue with the license change is the fact that it was so *subtle*! I was going to upgrade a Liquibase dependency only because of a transitive dependency's vulnerability...

With dialects producing quite different serialisations when reading the data, this seems inevitable. - MariaDB / MySQL produce the WKB as `byte[]` encoded text (`String.getBytes()` contains the data) when reading...

Oracle 23c now supports this: ```sql select json_array(select 1) ``` Producing: ``` |JSON_ARRAY(SELECT1FROMDUAL)| |---------------------------| |[1] | ``` Or also: ```sql select json [ select 1 from dual ] ```