"If an Oracle Database license is not an issue to a purchasing department, then a much less expensive jOOQ license won't be."
In my experience the equation rarely works that way. The decisions to buy Oracle and the decsions to buy such and such an application that will use a database are more often than not connected, not made at the same level, do not occur in the same timescale, etc. In working for small companies selling software solutions, time and time again we see the situation of a group (department, whatever) withing a company buying a small or modest software solution with a small or modest budget. The larger company owns an Oracle (or SQL Server or DB2 or whatever) license. The solution they are buying is required to use that database system. The fact that the larger company was willing and able to blow millions on Oracle has nothing to do with what its many departments are willing and able to spend in the many smaller purchasing decisions they make around software solutions. For much the same reason I can't build software that is tied specifically to PostgreSQL, as much I would like to. Selling that to such a place saying "this product is highly optimized for PostgeSQL...don't worry it's free" isn't going to fly. There is no arguing with the policy that "our company uses database X" for all database solutions. Often, when I begin writing a piece of software, it is a "venture" in a certain sense. I don't necessarily know what databases it will eventually need to be able to run on. It may eventually go into one of the above situations. I also may not know how (or if) it will be sold, and what kind of revenue it will justify. You are asking new software efforts when considering whether to use JOOQ to know (or bet on) that they will only ever use a non-commercial database, or that they will be able to justify the cost of your license. -- 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.
