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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
