Hi Eric, It is true that *some* setups will be at a disadvantage by the current licensing strategy, much like other licensing strategies will put others at a disadvantage. Another option might have been to follow suit with OneWebSQL and charge only for the code generator: http://onewebsql.com. For jOOQ, this would have put 80% of all users at such a disadvantage. So I agree with you, that there is a grey area of different shades of "I don't know if jOOQ is right". I would even say that this has been true for all previous versions of jOOQ. I can assure you that I don't underestimate those complexities, but I cannot address them all at once. This is why I keep trying to assure this group that I am open to discussion and to creative solutions. But I also want to start this business now, and I have to start somewhere, with some assumptions.
Now, when you buy a car, you don't just buy the cheap Fiat because of the "disadvantages" induced by the Ferrari, right? :-) You make an informed (or emotional) decision. So let's start again at looking at advantages, at the bright side. I think that by looking at the advantages, we'll find the best solution for jOOQ's future. For instance, by using jOOQ's typesafe API, generated code and all the SQL knowledge put inside jOOQ, you might be able to complete your project 20% faster, as you: - Make no syntax or data type mistakes - Write SQL much faster through IDE autocompletion - Take advantage of all the powerful SPIs to control SQL output - Can embed all your stored functions into SQL, typesafely Now, with Oracle in particular, the above advantage is extraordinary, as you get native jOOQ support for things like: - CONNECT BY - PIVOT clauses - Oracle UDTs with member procedures - I just registered a feature request about the partition extension clause from this thread: https://groups.google.com/forum/#!topic/jooq-user/hLojif16pXM I hope you stay with me on this matter. I think that by looking at advantages and added value, we'll find the best set of solutions for a dual-licensed jOOQ. I am fully aware that going from free to partially non-free leaves some uneasy feelings of surprise and regret. And I'm glad that they're expressed and (hopefully) addressed. But I'm very positive about this whole venture as I'm sure it will work out one way or another. It was the right time to make such a step. Lukas 2013/10/10 Eric Schwarzenbach <[email protected]> > Actually I've been assuming something about how this license works, that I > should verify: > > Suppose I've written a piece of software using JOOQ (and say it uses the > JOOQ Runtime module for execution) and sell this product to buy 5 companies > that will use it with Oracle. Does this mean that either they each have to > buy a JOOQ licence, or I have to buy those licenses and include them with > my product? I've been assuming that my buying a single license does not > cover me for however many copies of it I sell and get deployed on my > customers servers. > > Is this right or am I misinterpreting? > > -- > 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. > -- 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.
