And a few years later, MULTISET and MULTISET_AGG support have finally been added to jOOQ 3.15, see:
- https://www.jooq.org/doc/latest/manual/sql-building/column-expressions/multiset-value-constructor/ - https://www.jooq.org/doc/latest/manual/sql-building/column-expressions/aggregate-functions/multiset-agg-function/ - https://blog.jooq.org/2021/07/06/jooq-3-15s-new-multiset-operator-will-change-how-you-think-about-sql/ I'm really excited about this new feature. I think this is how SQL oriented folks really want to work with nested collections, as it fits the relational paradigm very well, at least if those ORDBMS extensions are accepted. Cheers, Lukas On Tuesday, January 6, 2015 at 10:45:20 AM UTC+1 Lukas Eder wrote: > Some feedback for this discussion. The state of the design vision around > nested collections in jOOQ will be aligned with what the SQL standard has > to offer. The SQL standard allows for MULTISET usage in SELECT clauses, > which is the SQL way to implement a nested collection. The relevant issue > is this one here: > https://github.com/jOOQ/jOOQ/issues/3884 > > JPA's joined nested collections are a workaround to materialise object > graphs. LLBLGen's prefetch paths are an alternative syntax for what should > really be multisets. > > We're currently evaluating how MULTISETs can be integrated in the jOOQ > API, and more importantly, how they can be emulated (at least partially), > where they're not natively supported in the underlying ORDBMS. Databases > with native support are: CUBRID, Informix, Oracle. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/98ba2f69-8d27-4117-bb1a-599603ed8405n%40googlegroups.com.
