2013/9/22 Stéphane Cl <[email protected]> > > OK, that should be rather easy to fix. Should be included in jOOQ 3.2, by >>> the end of September: >>> https://github.com/jOOQ/jOOQ/**issues/2761<https://github.com/jOOQ/jOOQ/issues/2761> >>> >>> >> > No doubt it's a valuable addition. > I figured out the things you are going to document the hard way and I am > sure it will make custom generators much more accessible. Thumbs up. > > >> >>>> And I think it is among the best ones ;-). Doesn't break compatibility, >>>> self documenting and and doesn't require much work. >>>> >>> >>> OK, I think that can be aligned with the newly suggested XML I've >>> mentioned further down. Another one for jOOQ 3.2, hopefully: >>> https://github.com/jOOQ/jOOQ/**issues/2762<https://github.com/jOOQ/jOOQ/issues/2762> >>> >>> >> > Even if you implement some sort of config-file based generator, it's still > useful! > > >> >>> >>>> Your proposition sounds good to me because you could define a generic >>>> default naming convention that would be fine for 80% of your particular DB >>>> objects and switch to table of field level when needed which is probably >>>> what most people need. >>>> >>> >>> Hmm, maybe I didn't stress enough the fact that the above XML >>> configuration will apply only when it matches. When it doesn't match, >>> jOOQ's defaults will apply. In other words, your use case is fully covered >>> by my alternative. You can provide an exact regex matching only one table >>> and then rename all objects for precisely that table. Except that you can >>> also match more than one table, if so desired. >>> >>> Does that make sense? >>> >> > It does, In fact I was satisfied with your xml schema idea but I didn't > express it clearly ;-). >
Alright ;-) > >> Early reviews / feedbacks welcome >> >> > I haven't yet migrated to 3, my project is successfully using 2.6 in > production. As the only thing I miss in 2.x is also not present in 3.x (it > has to do with mybatis-like transaction management) I did not upgrade. > Will consider migrating during the next week.. > I had studied MyBatis' transaction (session) management before. To me, it seemed to be tailored to only one JDBC transaction models, not JEE/JTA models, or alternative, third party models. What are the good parts of MyBatis' implementation, according to you? Cheers Lukas -- 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.
