Hi Roger, Good question. And probably a slight "license-vulnerability". The license agreement's annex defines some constraints on the Trial Edition:
*2.1.2 Termination of Trial Edition * The Trial Edition Subscription shall be automatically terminated 30 days after Delivery onto a Workstation, after which it must be immediately removed from such Workstation. Without the written consent of the Supplier, Customer is not entitled to install the same Major Release of the Software on the same Workstation again under the terms of the Trial Edition Subscription. So, you can check your application's SQL Server compatibility once per Workstation and Major Release. jOOQ's licensing strategy generally doesn't keep you from implementing a 15-people, 5-year project against MySQL, and then switching to SQL Server in the last month of the project. But I'm pretty sure, if you were to do this, your application will terribly fail and the money saved on jOOQ licenses will be lost again in eternal bugfixing sessions :-) But anyway, thanks for pointing this out. This shows that the "Express Edition" license that we've discussed in another mail will have to include some additional limitations to prevent such a scenario... About your version sync concerns: Yes, the OS / Trial / Professional / Enterprise versions will remain in sync, also for future releases. There are no plans to reduce the feature scope or delay releases for the OS version. Do note, however, that the Trial version might have other limitations, such as a "synchronized (SomeClass.class)" in the query execution code. I might also limit the number of executable queries per application execution, which will make it unusable for pre-existing, large applications built on "jOOQ Open Source Edition". It is really intended to be a Trial version to assess whether jOOQ should be used at all, or not. Cheers Lukas 2013/10/12 Roger Thomas <[email protected]> > As a follow up, > > Will the OS and Trial releases found on the download page of the web site > be in sync going forwards (so all the same release). I don't need to code > against MSSQL and I may never need to deploy anything I write to MSSQL, but > I do need to make sure that once in a while I check that it all works > against MSSQL as its the market leader in the Windows world. So being able > to pull down the Trial release once in a while will work fine, but only if > its the same code base as the OS release. > > Thanks. > > Roger > > > On Saturday, October 12, 2013 1:04:28 AM UTC+1, Roger Thomas wrote: >> >> OK, as everyone out there has to eat I can't argue against you trying to >> generate a living from all the work you have put into this product. >> >> One thing, have you considered setting the licence up in such a way as to >> still allow the open source licence to allow deployment against the Express >> version of MSSQL? This is a free release from MS that basically is deployed >> as a background service by many Windows applications. >> >> Roger >> >> >> On Wednesday, October 9, 2013 8:33:01 PM UTC+1, Lukas Eder wrote: >>> >>> With the new jOOQ 3.2, apart from introducing great new features, we are >>> changing quite a few things on how we operate. At Data Geekery GmbH, we >>> believe >>> in Open Source. But we also believe in the creative power enabled by >>> commercial >>> software. This is why we have chosen to implement a dual-licensing >>> strategy. >>> Read more about this strategy here: >>> >>> http://blog.jooq.org/2013/10/**09/jooq-3-2-offering-** >>> commercial-licensing-and-**support<http://blog.jooq.org/2013/10/09/jooq-3-2-offering-commercial-licensing-and-support> >>> >>> But jOOQ 3.2 also ships with great new features! They include: >>> >>> A new RecordListener SPI which can be hooked into the Configuration in >>> order to >>> control ActiveRecord lifecycle events. This is very useful if you want to >>> initialise some database records prior to inserting new data, or if you >>> want to >>> implement a central ID generation strategy, e.g. by generating Java >>> UUIDs. >>> >>> A new, experimental VisitListener SPI which can be hooked into the >>> Configuration >>> in order to control jOOQ's complete QueryPart rendering and variable >>> binding >>> lifecycle. Use this powerful SPI to perform custom SQL transformation, >>> e.g. to >>> implement shared-schema multi-tenancy, or a security layer centrally >>> preventing >>> access to certain data. >>> >>> With this release, the Oracle and DB2 SQL dialect families will now be >>> able to >>> distinguish Oracle 10g, 11g, 12c features, as well as DB2 9.x, 10.x >>> features. >>> This is important as more and more databases start supporting the SQL >>> standard >>> OFFSET .. FETCH clause and other clauses that are emulated by jOOQ. >>> >>> The code generator has experienced a lot of improvements, mainly >>> including a new >>> MatcherStrategy, which can be configured through Maven or XML code >>> generator >>> configurations. This generator strategy will allow you to implement >>> several >>> regular-expression based naming pattern replacements for all sorts of >>> generated >>> artefacts. This is extremely useful to generate table, record, pojo >>> class name >>> prefixes, suffixes in particular, or to just completely redesign the way >>> the >>> jOOQ code generator generates things. >>> >>> For more details, see the release notes: >>> http://www.jooq.org/**notes<http://www.jooq.org/notes> >>> >> -- > 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.
