Hi Witold, Thank you very much for your feedback!
2015-12-30 15:46 GMT+01:00 Witold Szczerba <[email protected]>: > Hi, > since we have a special chance to have our say :) I would like to mention > about the thing which makes a little trouble now. Let's say I have a class > WalletId. It's just a wrapper around String, VARCHAR in SQL. The trouble > is, if I want to do a custom mapping for some columns in tables to use > WalletId, I have to split the project to have two artifacts. So, instead of > one POM, we need now 3: one for the WalletId class, second for the rest of > the project and third, a parent for those two. In Microservices, when all > the modules are really small, it is even more annoying. > > Question is: is it possible to mix the process of code generation with the > project's compilation phase, so we could get the auto-generated code to use > the types from that module itself? > Sure, those types don't need to be compilation-ready while you generate your code. Unless, of course, you want to load the types in your own, custom code generator enhancement. But the code generator config only refers to types as fully qualified names (strings), so there's no dependency. The correct Maven phase for this would be generate-sources, or generate-test-sources. Or am I misunderstanding something? > Other things on my hypothetical wish list would be to support non-JDBC > drivers. As we know the JDBC is a blocking API, but there are alternative > drivers for some databases using async techniques. There is a lack of > standardization in this area, but in my imaginary, perfect world :) the > projects like jOOQ could try to change the JVM world in this area! OK, I > was just thinking loudly :) > This is on my wishlist, too :-) But it doesn't have anything to do with the code generator. > I won't even mention support for Clojure. Such a feature would cost a lot > of time and I guess it would be doable by a 3rd parties if such a desire > would emerge. > Why not? It might be worth looking into. There is Suricatta, a third-party library that builds on top of jOOQ. Perhaps, the jOOQ code generator can be enhanced to also generate Clojure artefacts. -- 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.
