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 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.
