I'm not sure what exactly you're looking for, but these are some out of the box alternatives to connecting to a live database instance for code generation:
- https://www.jooq.org/doc/latest/manual/code-generation/codegen-jpa/ - https://www.jooq.org/doc/latest/manual/code-generation/codegen-xml/ - https://www.jooq.org/doc/latest/manual/code-generation/codegen-ddl/ - https://www.jooq.org/doc/latest/manual/code-generation/codegen-liquibase/ Note that it's not uncommon to spin up a "live" database using testcontainers just for code generation (and integration testing): - https://blog.jooq.org/using-testcontainers-to-generate-jooq-code/ I hope this helps, Lukas On Mon, Oct 17, 2022 at 9:07 AM akash verma <[email protected]> wrote: > Hello lukas, > > First of all, thank you for all your replies and for such quick support. I > am really thankful. > > I want to ask as of now JOOQ is generating the POJOS from the SQL Script > and Databases. > Did JOOQ have different methods for reading from scripts and from > databases? > > for example:- > "Assume that as of now, JOOQ is generating Pojos only from the > Databases and we want to generate it from the Script now, how and where we > should inject our script in JOOQ?" > > -- > 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/cf4068f3-0cf3-4ec3-89f5-3985b5448af1n%40googlegroups.com > <https://groups.google.com/d/msgid/jooq-user/cf4068f3-0cf3-4ec3-89f5-3985b5448af1n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAB4ELO40%2BePbguVC4ywakJ%2Bww6vNikV_pMP7gxVmHBwUuDja2g%40mail.gmail.com.
