Lukas Eder

Maybe. Though, it's very easy to add support yourself. Just look at the other range type support for inspiration.

I'm closing this issue as "worksforme" as related issues have been addressed by now: - https://github.com/jOOQ/jOOQ/issues/12872 - https://github.com/jOOQ/jOOQ/issues/13031 I'm not entirely sure if this is the same issue as the...

It looks like this is the same issue as https://github.com/jOOQ/jOOQ/issues/15048, which I've just now fixed for jOOQ 3.19.0, 3.18.5 (https://github.com/jOOQ/jOOQ/issues/15062), 3.17.14 (https://github.com/jOOQ/jOOQ/issues/15063), and 3.16.20 (https://github.com/jOOQ/jOOQ/issues/15064)

Duplicate of https://github.com/jOOQ/jOOQ/issues/15048

#12985 (still!) hasn't been prioritised yet, so I suspect we can simply update the manual as requested here. Instead of: ``` myConfigurationName(sourceSets.main) { ... } ``` We'll generate ``` generationTool...

Fixed. The manual will be updated within ~2h

Tried this again. I *still* cannot use `JSON_ARRAYAGG()` on MariaDB as I've found another show stopper: https://jira.mariadb.org/browse/MDEV-31159 This leads to all sorts of problems when nesting such content, as hinted...

A recent fix seems to have improved this: ``` 13:18:37,793 DEBUG [LoggerListener ] - Fetched result : +----+----+----+ 13:18:37,793 DEBUG [LoggerListener ] - : | id| id| id| 13:18:37,793 DEBUG...

Closing this as won't fix. The reservations were justified, and the leaking of `Map` into public API of the `Record` type isn't acceptable.

I mean, we could generate record subclasses of type `GeneratedType & Map`, but that sounds even hairier!