What I'm working on is a platform that is largely DB agnostic. The data access patterns are trivial and, with the great help of jOOQ, it should run on any DB. So I write my platform, which is open source, and produce a release. I would then like to enable somebody else to pick up my release, and if they choose to buy a jOOQ license, run my platform on a non-OSS database. If somebody wishes to use a commerical version of jOOQ I won't want to force them to recompile the platform. For practical reasons, I would like them to run the same signed releases that I've produced so that I can ensure that what they are running is the same binaries that I've done my QA against.
Since what I've created is a platform, I also want to enable people to use commercial versions of jOOQ and take advantage of the powerful features of their DB. So the platform is DB agnostic, but the extensions people write on top of my platform may be specific to a DB or leverage commerical features. Darren On Mon, Jan 20, 2014 at 10:48 AM, Lukas Eder <[email protected]> wrote: > Hi Darren, > > Apart from legally interesting aspects of your enquiry, what is the reason > you do not want to compile against the commercial version from the > beginning? > > From a merely technical point of view, the jOOQ Open Source Edition contains > a subset of the jOOQ Enterprise Edition's source code, API and ABI. Going > from OSS to Professional/Enterprise should certainly be feasible. > > Cheers > Lukas > > > 2014/1/20 Darren S <[email protected]> >> >> I'm currently writing some code that is intended to work across multiple >> databases and as such nothing is really using any DB specific features. I'm >> only using and testing open sources DBs at the moment but I have every >> intention of supporting SQL Server. I was wondering though if there is ABI >> compatibility between the commerical and OSS versions. Specifically, can I >> compile against the OSS version and then ship with the commerical version >> for SQL Server. I currently pick the dialect based off of configuration, so >> I do something like >> >> SQLDialect.valueOf(database.trim().toUpperCase()) >> >> Obviously If I take advantage of any SQL Server specific functionality, >> then I would need to compile against the commercial version for that module. >> But again, I don't wish to compile the entire platform against the >> commerical version, if possible. >> >> Darren > > -- > You received this message because you are subscribed to a topic in the > Google Groups "jOOQ User Group" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jooq-user/DmhmO7J9380/unsubscribe. > To unsubscribe from this group and all its topics, 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.
