I'm a backend developer who worked in South Korea.
I'm experiencing a mysql dependency conflict.
I want to use two data sources (DB: mysql) in a spring boot project, but the mysql version is different (one is 5.0 and the other is 8.0).
So, I add a dependency like this in build.gradle.
runtimeOnly("mysql:mysql-connector-java:5.0.4")
runtimeOnly("mysql:mysql-connector-java:8.0.22")
However, if the group and name are the same, Gradle only supports one dependency.
Who could think like this, the MySQL 8.0 connector can connect to the most recent MySQL version, so I verified that the MySQL 8.0 driver can connect to the most recent MySQL version, which is 5.7.
The other method I discovered is that MySQL 5.0 is connected via mysql-connector-java, and MySQL 8.0 is connected via mariadb-java-client.
But I don`t want to solve this problem like this... This is just makeshift.
Please give me another way. Thank you
In Gradle, how do you install multiple versions of the same dependency?
Related
I'm installing Jira locally with the latest version (7.13 x64 version).
When doing the custom install and trying to switch to using MySQL as the database,
I get the error:
You have specified a database that is not empty, please specify an empty database.
The database is brand new, I literally just created it and if I query it I can see it has no tables created.
I created the database (and several others) using either the standard CREATE DATABASE ... or be specifying UTF-8 as well, which is how the Atlassisn docs suggest it is done.
But, no matter what I do, the same error keeps appearing. Topics on the Atlassian site mentioning this error haven't been any help and all seem to do with version conflicts which aren't relevant here.
I have installed the Java/MySQL connector version 8.0.13. Is it something to do with that?
Thanks in advance.
It was the JDBC connector that was the problem. I downloaded and installed the latest (version 8.0.13) but it was causing the error.
Installing version 5.1.47 works just fine, even though it isn't recommended for use with MySQL 5.6, which I'm using.
But, using that connector, I have a database installed and Jira is functioning as it should.
I know is so late for answer but say answer to other searcher this question
I found this error in the logs which lead me to https://jira.atlassian.com/browse/JRASERVER-67274
Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
The long and short of it is you need an older mysql-connector-java-5.1.x.jar driver instead of the latest mysql-connector-java-8.0.x.jar that the documentation would lead you to install.
Reverting my driver to mysql-connector-java-5.1.49.jar fixed the issue for me.
tl;dr: SonarQube calculates lines of code metric for some projects but not others after an upgrade.
Hello everyone,
I recently took over an orphaned SonarQube 5.1 installation running on MySQL 5.1 on another server. When I upgraded SQ to 5.6.2 it told me that it required MySQL 5.6. Because the servers in question are CentOS 7 that version of MySQL is not available through yum. Use of yum is required for installing software. I installed PostgreSQL on the SQ server and, because I did not want to lose SQ history and configuration, migrated the database from MySQL to Postgres using pgloader (see pgloader.conf in code block below). The migration appeared to have worked as the schema changes 5.1->5.6.2 succeeded as did 5.6.2->6.1.
LOAD DATABASE
FROM mysql://USER:PASSWORD#mysqlhost.my.com/sonar
INTO postgresql://USER:PASSWORD#pghost.my.com/sonar
with create indexes, preserve index names;
However, some projects that existed before the upgrade and migration and also some projects that have been added (through Jenkins) after the migration never have the Lines of Code metric calculated. These are primarily but not exclusively C# files.
I don't see any way to "reset" a project in the UI or web API. If I could export the SQ configuration, I would wipe the database and reload, but I don't see a way to do that either. Starting from scratch is undesirable. Any help is greatly appreciated.
Upgrading the database version needs intensive testing.
Is it better to upgrade to latest version of MySQL workbench?
If we are installing previous versions of MySQL database, Is there any certification matrix to know all the corresponding version of MySQL workbench or what minimum version it can work with?
Mysql-Workbench using libmysql.dll. You must update this dll from your mysql\lib folder. So a lot function working same as before.
I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.
What is the best version of MySQL to use with Rails 3 as of today (28/4/11)?
At the moment I got Mysql 5.5.11 community server and I have had lots of problems with it. I want to install an older version of MySQL. Which one would you recommend?
Thanks in advance.
PS: The issues were with the mysql2 gem.
I would say 5.1 only because of problems I had trying to compile the driver with MySQL 5.5 on mac (which is of course a show stopper).
And I had no issues at all with MySQL 5.1.
Even with the very public outage it recently suffered, we would recommend Amazon's RDS service. We find it has been very reliable and easy to administer.
Our RDS instance is currently running MySQL version 5.1.45.