Hi

I'm brand new to jOOQ, so maybe I'll be saying stupid stuff, don't hesitate 
to tell me if so.

Anyway, after having played with it various points came to me:

A - my need is for a brand new use case, without existing tables. To start 
from scratch is currently annoying. I need to create the tables and the 
like, using string constants for names, and then generate the model, and 
then update my tables creation script with the constants in the generated 
classes. Yet I'm coming from Java and, actually, some Java model of my 
domain. As such, it would be nice if, somehow, I could describe my tables 
and then have the pojo generated and as well a creation script. So 
basically I'm all for JPA annotations support, or something else if needs 
be (I'm unsure JPA "philosophy" fits with jOOQ "all of SQL" concept, but 
then one could complete the edge case on his own).

B - even without going as far as A, when the model is generated from DB it 
would be nice to have the creation script created too. 

C - immutable POJO: I really like the peace of mind immutable objects 
provide. It would be awesome if I could tell the generator to create 
immutable pojos only.
 
Regarding your others questions :
1 - target languages, forms
IMHO the generated code is tightly coupled to the DSL itself. So to me it 
feels like the question is more about the whole lib than just the pojo. 
Still, being written in Java, it should be usable from most of the others 
JVM languages. Maybe going for an immutable approach would help for 
integration with Clojure or Scala code, but once again then is about the 
whole public API then, which is quite bigger from the generator itself.

For the others points, well, can't tell much apart from the obvious, so 
I'll skip ;)

Thanks a lot for jOOQ and hopefully it wasn't all nonsense!

Happy new year

best
joseph

-- 
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.

Reply via email to