Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the problems encountered when the Mysql database is upgraded from 5.6.28 to 8.0.11 to deploy the project

2025-01-17 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to solve the problems encountered when the Mysql database is upgraded from 5.6.28 to 8.0.11. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

The problems and solutions encountered when deploying the project during the upgrade of mysql database version from 5.6.28 to 8.0.11 are described as follows:

First of all, this project uses hibernate4.2.0, link mysql5.6.28 is no problem, change to 8.0.11, start the error report

1.Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set

If you report an error, configure it.

The startup project did not report an error, but the visit project reported an error.

two。 Access error com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Client does not support authentication protocol requested by server; consider upgrading MySQL client

The reason is: the configuration process of Authentication Method in the process of installing mysql8 is based on different encryption methods. If you choose the first strong encryption, you will have the phenomenon I described earlier; you should choose the second verification method, that is, to retain the old encryption method.

So there are three solutions:

1. Reinstall mysql8, pay attention to the second choice, and retain the old encryption method.

2.MySQL Installer can modify Authentication Method configuration directly

3. Perform statement modification directly

Mysql > ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY' 123456 question OK, 0 rows affected (0.11 sec) mysql > FLUSH PRIVILEGES;Query OK, 0 rows affected (0.01 sec)

Note: root is the user name, localhost refers to the local machine, mysql_native_password is the old password authentication mechanism, and 123456 is the password

This is the end of this article on "how to solve the problems encountered when the Mysql database is upgraded from 5.6.28 to 8.0.11". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report