2013/7/30 <[email protected]> > Wow, thanks for your awesome and detailed response!
No worries. > What is your experience running jOOQ with Drizzle in general? >> > Apart from this issue with getting table names, none yet. Note that I'm > only using the JDBC connector from Drizzle, I'm using MySQL as the actual > server for the moment(though planning to move to MariaDB). > Note that jOOQ 3.1 officially supports MariaDB: http://www.jooq.org/notes.php?version=3.1 This includes integration testing against an actual MariaDB instance and the official MariaDB JDBC driver. What is the reason you chose Drizzle rather than MySQL (or MariaDB or even >> CUBRID). >> > I was after a BSD alternative for the Oracle MySQL JDBC connector. I > hadn't head of CUBRID but I see it has a BSD connector. That might be a > viable alternative(for both the connector and maybe even the server), > thanks, I'll check it out. > CUBRID isn't a MySQL fork, but aims for replacing MySQL in web contexts. I haven't used it in production, but I'm impressed with its tool chain, given that it is a relatively new database, created by the Korean NHN corporation. But if this is just a licensing issue, then MariaDB is probably your best replacement for MySQL, given that the lead developer was the original MySQL developer. Do you know who's behind Drizzle? >> > Apart from what I gather from their website, no. OK, thanks! Lukas -- 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.
