Lukas, Maybe you've already considered this, but let me point out one consequence of this in the form of my own real life case: I'm currently working on library in which I am currently making use of JOOQ. My intention is to release this library as open source. My intention is also for it to work with any database. With this license change, I don't think I can do so. So I will be seriously considering abandoning the use of JOOQ in this tool. I will probably have to.
My company makes another product (not open source) which can work with any database (it has a small module which makes a couple of adjustments for different database vendors...it isn't complete and we only add to if we have a customer who wants to use a database we haven't yet added support for). This product doesn't use JOOQ but I've mused before that I might if I were do the intial work today, and if I were ever to rewrite certain parts of the system I would consider using JOOQ. So to speculate on the case of if the product did use JOOQ, this would complicate our licensing and we would probably have to charge an additional fee for customers that wanted to use a commercial database. I can't say whether we would or wouldn't do that, but I'm just saying this would be a complication and some level of discouragement to using JOOQ. This is also going to be deciding factor for many people looking for a tool like this and making JOOQ or QueryDSL choice. I understand why you might make this change, and of course there are trade offs.I'm not intending to criticize your choices, just to give some feedback on how it may relate to your users' choices. It is with no hard feelings but with some regret, that I suspect I will be working with JOOQ somewhat less in the future. Best regards, Eric -- 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.
