Hi Thomas, Thanks a lot for your comments. I'm very curious about some examples of what you have done:
2017-02-27 13:17 GMT+01:00 Thomas GILLET <[email protected]>: > What I've done for now is: > - extend the JavaGenerator to generate properties (i.e > field/getter/setter) in generated records (or POJOs) based on foreign keys > - write code to fetch records from a table and its "children" tables, and > then associate children records to their parent (that is create a graph) > using generated setters > - write code to insert/update/merge/delete a graph of record objects, > copying foreign key values from parent to children when needed > Perhaps there's already a low-hanging feature request that could be extracted from the above and moved into core jOOQ. > For fetching it's a lot less than what a MULTISET can offer I guess > You bet. Check this out: https://twitter.com/lukaseder/status/832939068933681152 Getting all actors, and the categories they played in, as a nested collection, and the films per category they played in as a doubly nested collection. Beautiful! :) > but the idea was to have write capabilities too (so you can insert/update > a graph right from deserialized JSON). > And for now I only handles one-to-one and one-to-many relationships. > Just to get the complete picture: Materialising a 1:1 entity graph that is supposed to be written back to the database later on is exactly the main value proposition of JPA. What currently keeps you from using JPA? Cheers, Lukas -- 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.
