On Wed, Jul 21, 2021 at 11:02 PM Manuel Rossetti <[email protected]> wrote:
> If I understand the CustomX classes, I could in theory I derive my own > concrete implementations of those classes and potentially use those > abstractions. I could then get instances of CustomRecord, for example, and > essentially use it like Record, etc. I guess the advantage would be that > then what I do does not depend on the internal API, right? I will have to > investigate it further. It's the current way of allowing to access otherwise internal API. It's not as good as https://github.com/jOOQ/jOOQ/issues/7444 will be, hopefully. > For a small database, I plan to show students how to: > 1) use JOOQ code generation > 2) use the generated classes for basic CRUD operations > 3) illustrate some DDL and some query building > > I will be assigning them a homework where they have to repeat the process > on another database, fill the database, and do some basic CRUD. The fact > that JOOQ generates the code makes this process have a lot less friction. > Working with Results and Records is just so much easier. The class is an > undergraduate introductory course on database concepts. > Great! Thanks for sharing :) -- 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/CAB4ELO5ov2%3D5PNgXei45OfUsFRHn4cMPeD09EYiDwsZrPc_G6w%40mail.gmail.com.
