Hi Shyam, Finding the "correct" procedure / approach to integrate a source code generator into your development and build processes is a challenging task and it depends on your existing development processes, team size, database setup and much more.
Some people prefer to have a single "master database" from which they generate source code. Others prefer to have several "developer databases" from which each developer generates their own local dev-version of the generated source code. Then, you should ask yourself if you want to put generated code under source control or if it should be generated on the fly by your build. Both are viable approaches, each with their own advantages and disadvantages. You can even implement your own "Database" (from jOOQ-meta) and provide jOOQ's code generator with your own database meta information, e.g. from an XML file. This may be useful if you work with an ERD design program or a database modeler. Future versions of jOOQ may actually provide such "Database" implementations Having said so, we don't really recommend one way or another, as it is very specific to your own environment. Cheers Lukas 2014-02-05 17:26 GMT+01:00 Sha <shatestt...@gmail.com>: > Hi Lukas, > I was going through the jOOQ manual , I come across a statement > something like this : > > "In addition to using jOOQ as a standalone SQL builder, you can also use > jOOQ's code generation features in order *to compile your SQL statements > using a Java compiler* against an actual database schema. This adds a lot > of power and expressiveness to just simply constructing SQL using the query > DSL and custom strings and literals, as you *can be sure that all > database artifacts actually exist in the database, and that their type is > correct*." > > To make use of above high lighted features. i.e. "t*o make sure* *all > database artifacts actually exist in the database, and that their type is > correct" *while java compile time. Is there any specific order we need to > follow ? > > To make my question more clear, I have done the following things. > *Step 1 :* Generated POJO against a DB using jOOQ Code Generator > *Step 2 : *Using those POJOs java classes written equivalent to SQL > stored procedures using jOOQ DSL- API. > > Tomorrow to make sure all database artifacts actually exist in the > database, and that their type is correct at the java compile time. What is > the correct procedure / approach? > > Thank you. > ~Shyam > > > > > > -- > 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 jooq-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
