I have a distributable open-source plugin for game servers (java-based) that's very heavy on database interaction and I'm looking for a solid query-building solution. I've been giving jOOQ a try because the database abstraction appeals to my users, and the ability to export the final query for debugging is appealing to me.
However, the application itself doesn't yet need most of what jOOQ offers. I really don't need any active record, any sql support outside of selects, insert, deletes. Our plugin is 512kb, but with jOOQ shaded (using minimizeJar) it grows to 1.5MB. That's a lot bigger and is going to lead to a bunch of problems. I haven't even looked at how much more memory the plugin uses when running. I haven't found another solution that's as flexible, so I'm searching for a way to strip down the jOOQ classes we're shading into our JAR, so that we can exclude features we don't (yet) need, but so far it doesn't seem possible. If that's not possible, are there any alternatives I might look at? -- 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.
