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]. For more options, visit https://groups.google.com/d/optout.
