For what it's worth, running the jOOQ integration tests using the MariaDB JDBC driver against a MySQL database yields 12 failures in 283 test suites. 4 of them are known issues on the jOOQ 3.3 branch, the rest boils down to:
- Issues when calling stored procedures - Issues when using ResultSet.CONCUR_UPDATABLE - Wrong implementation of Statement.getGeneratedKeys() (e.g. https://mariadb.atlassian.net/browse/CONJ-39) - Some DatabaseMetaData bugs (e.g. https://mariadb.atlassian.net/browse/CONJ-66) So, from a jOOQ perspective, if you're not using stored procedures, that's an OK result, I guess. 2013/10/19 Ian Clarke <[email protected]> > I'm not very familiar with the underlying protocol network protocol for > MySql, but my suspicion here is that it is very simple, which would make > incompatible changes extremely unlikely. > > That being said, our app is SAAS so in reality this is a non-issue - > lawyers love to lawyer... :-) > > > On Fri, Oct 18, 2013 at 5:47 PM, Roger Thomas <[email protected]>wrote: > >> This has always been open to debate as languages like Java do not static >> statically link libraries to a compiled application in the same way that C >> compilers do and so the JDBC driver does not become part of your >> application. What is clear is that MySQL/SUN/Oracle all have wanted to make >> sure that the work they have put into their JDBC driver is not just taken >> and converted into a closed source JDBC driver for some other database >> project. >> >> Common pratice seems to be to not include the MySQL driver with the >> application and instead have the end user download it and then place it >> into the correct directory so that the application >> can find it at run time. Going forwards this will be a simpler option >> than trying to support the MariaDB driver running against Amazon's >> deployment of MySQL. I would guess that Amazon does all of it's system >> testing and support using the MySQL based drivers, so every change at their >> end will put your application at risk. >> >> Roger >> >> >> >> On Friday, October 18, 2013 10:04:39 PM UTC+1, Ian Clarke wrote: >>> >>> We're going through a legal due-diligence process, which revealed (to my >>> unpleasant surprise) that the MySQL java connector library is GPL, not >>> LGPL. >>> >>> I have read that the MariaDB connector library can be used as an LGPL >>> alternative to this. I see that Jooq has MariaDB support, however we are >>> using Amazon RDS, which I believe is MySql. >>> >>> Can anyone confirm that we can use the MariaDB connector library to talk >>> to RDS via Jooq? If so, what do we need to modify to do this? >>> >>> Many thanks, >>> >>> Ian. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "jOOQ User Group" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jooq-user/4XpEa1dRMUY/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Ian Clarke > Blog: http://blog.locut.us/ > > -- > 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. > -- 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.
