Blog post: support for MariaDB and MySQL backends #8577
Conversation
| ``` | ||
|
|
||
| 2. Declare the JDBC datasource to use as `mariadb` (_this should be done regardless of whether you | ||
| are using MariaDB or MySQL_): |
There was a problem hiding this comment.
Could we have mysql as an alias for user convenience? I imagine MySQL users will tend to think about their datasource as "MySQL" in daily activities... The JDBC URL will remain jdbc:mariadb:, of course, but config-wise it might be easier for users to manage quarkus.datasource.mysql.username=my_user. WDYT?
There was a problem hiding this comment.
Interesting idea! Yes, I think we can add a 3rd datasource quarkus.datasource.mysql, its db-kind must be mariadb of course, but it could make the user XP slightly better indeed. Besides, if there are specificities for MySQL, these could easily go under quarkus.datasource.mysql.jdbc.additional-jdbc-properties without affecting MariaDB connections.
Also, it might be possible to create a ConfigSourceInterceptor that would transparently change jdbc:mysql to jdbc:mariadb in all JDBC urls.
No description provided.