I'm currently working as a dev for a large-ish company. I have the option of building a new support tool for lower environments (i.e. non-production, very boring DB reads + logic scenario) but it needs to support a few different databases, most of which are open-source, one of which is Oracle.
I can maybe use some new tech, especially if I can justify it in terms of implementation speed. I use JOOQ for my personal stuff (on postgres) and I think it would be a good fit for what I need to do - but I probably won't be using it because I can't (won't) invest the time trying to convince folks overseas to buy it. I think the current license model hurts JOOQ's ability to be used in "gentle introduction" scenarios that developers often use to evangelise new tools. Short term: Would the old open source 3.10 branch work for this purpose? Is that why it still gets the odd bug-fix release? Are pull-requests on the 3.10 branch welcome? Long term: Would you consider a "low functionality" mode for JOOQ, where it can talk to pro-supported databases, but only uses a sort of "lowest common denominator" pure-SQL mode? Or possibly a license tier for "non-production" purposes (this idea's a bit iffy, I'd predict a lot of uncertainty over the definition of production)? -- 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/d/optout.
