Hi Roger, Thank you very much for the feedback. Yes, I have considered creating specific price plans for SQL Server Express and Oracle Express. The general licensing strategy connects the "jOOQ Open Source Edition" to "open source databases", not to "free databases". So, express edition support will not be included in "jOOQ Open Source".
However, I'm gathering feedback in the next 1-2 weeks and work out another, cheaper price plan than "jOOQ Professional Edition", which grants access to SQL Server Express and Oracle Express in addition to all the OSS databases. Such a license will be available for jOOQ 3.2, then. Cheers Lukas 2013/10/12 Roger Thomas <[email protected]> > 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.
