总结解决 No suitable driver found for jdbc:mysql//localhost:3306/ 问题的解决方案,各种情况都已囊括,希望可以帮助到有需要的各位

最新推荐文章于 2024-03-13 23:30:00 发布
最新推荐文章于 2024-03-13 23:30:00 发布
阅读量1.1w 收藏 27
点赞数 12
分类专栏： java 文章标签： mysql 数据库 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_41413485/article/details/125973933
版权

懂得都懂,看着这几行报错看了好几天,差点吐血!

 查遍全网,无一例外,都是总结为以下三个问题:

1.URL格式问题,数据库名后面加一串声明之类的

(事后证明url有无声明跟连接数据库毫无关系)

2.驱动字符串

(其实只要是比较高版本的jdk,都会像下图一样报错并提示驱动字符串要加cj.而不是报No suitable driver,所以并不是这个问题)

 

driver=com.mysql.cj.jdbc.Driver
driver=com.mysql.jdbc.Driver


3.Classpath中没有加入合适的mysql_jdbc驱动

(意思就是假如数据库版本5.0.x要对应驱动包版本5.0.x,假如数据库8.0.x要对应驱动包8.0.x,这是笔者在最后把问题解决的前提,所以读者一定要先把版本先对应好)

可是检查了上述问题的地方过百遍,没有任何问题,都快要砸电脑了!!!!!!

但是最后,终于,终于,终于找到问题所在!!

原来笔者电脑上居然安装了两个MySQL,一个是5.1版本,一个是8.0.29最新版,而且两个数据库的端口都设置成了3306(而且之前在安装MySQL时,环境变量居然也没有配置好),这就导致我对自己电脑数据库的认知出现错误(以为我的电脑只有一个8.0.29版本的MySQL),因为我使用的SQLyog默认连接的就是MySQL8.0.29版本的MySQL,我之前用命令行进入MySQL时,我一直以为我在使用8.0.29版本的MySQL(事后才知道用命令行默认进入的是MySQL5.1,怪不得之前把进程里的一个MySQL进程关闭后再进入命令行中的MySQL后,显示的表才能与SQLyog对应上,因为这操作是从本站某篇文章<命令行里的数据库和SQLyog数据库对应不上>看到的处理方法,文中说道:只要把进程里的MySQL进程关掉后在命令行上重新通过cd进入MySQL路径打开MySQL就能对应上SQLyog的数据),

所以最后总结:导致报错的原因可能有两个,

一是MySQL环境变量没有配置好,导致eclipse压根没办法找到8.0.29版本MySQL的打开路径(这是大概率问题所在,所以读者假如在文章开头写的三个问题都尝试过还是报错No suitable driver的话,就可以检查一下自己的MySQL的环境变量配置有没有出现问题),

二是电脑上装有不止一个MySQL,而且端口都是一样的,有可能就导致了无法正常连接数据库了(检查电脑上是不是装了多个数据库,发现是的话,可以检查环境变量写的路径是不是自己一直在使用的数据库的路径,同时把其它不用的数据库都卸载干净).

此外,笔者由于是初学者,所以在最终解决问题之前还尝试了很多思路去解决问题,以下列出以供各位读者参考,各路高手勿喷.

是不是jdk版本问题或者是不是eclipse版本问题

因为笔者看到有文章提到报错No suitable driver的同时驱动是加载成功的,所以是因为8.0.x版本的MySQL既要与8.0.x版本的驱动jar包对应还要与13.0版本的jdk对应,所以笔者就去尝试把jdk更新成13.0版本,但是发现eclipse版本巨旧(在java1234课程里下载的版本)导致无法使用13.0版本的jdk,所以就又去把eclipse更新成最新版本,然后把jdk更新成13.0,发现还是不行,所以与eclipse版本无关,也与jdk版本无关,因为最后找到原因所在后尝试使用哪个版本的jdk都可以连接成功的.

是不是MySQL版本和驱动jar包版本问题

其实是有关系的,但是文章开头陈述的三个问题解决方案中已经写到,只要8.0对应8.0,5.0对应5.0,正常导入到build path就把问题解决了,所以与笔者最后解决问题关系不大,只是解决问题的前提而已.

JRliuzz
关注
  • 12
    点赞
  • 踩
  • 27
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
JDBC操作MySQL数据库出现：No suitable driver found for...异常
weixin_45965432的博客
01-08 1万+
JDBC操作MySQL数据库出现：No suitable driver found for …异常，可能原因如下： 一、没有导入jdbc驱动jar包 导入方法如下： 点击 IDEA 左上角的 File -->
完美解决ntp的错误问题no server suitable for synchronization fo
01-20
当用ntpdate -d 来查询时会发现导致 no server suitable for synchronization found 的错误的信息有以下2个：  错误1.Server dropped: Strata too high 在ntp客户端运行ntpdate serverIP，出现no server suitable for synchronization found的错误。 在ntp客户端用ntpdate –d serverIP查看，发现有“Server dropped: strata too high”的错误，并且显示“stratum 16”。而正常情况下stratum这个值得范
java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/
weixin_30690833的博客
07-12 845
出现这个异常原因可能很多： 1.编码问题 2.没有加载类驱动：换一种数据库的连接方式，就忘了这个：Class.forName(driverclass); 1 import java.io.IOException; 2 import java.io.InputStream; 3 import java.sql.Connection; 4 import java.sql.Dri...
解决 Java 错误 Java.Sql.SQLException: No Suitable Driver
最新发布
迹忆客
03-13 1377
本篇文章介绍了 Java 中的错误。
Code of practice for information security management AS/NZS ISO/IEC 17799:2001
01-20
This Standard was prepared by the Joint Standards Australia/Standards New Zealand Committee IT-012, Information Systems, Security and Identification Technology and supersedes AS/NZS 4444.1:1999, Information security management, Part 1: Code of practice for information security management. It is identical with ISO/IEC 17799:2000, Information technology—Code of practice for information security management and differs in only very minor editorial details from AS/NZS 4444.1:1999. However the Standard number has been changed to that of the international Standard (ISO/IEC 17799) to minimize any confusion when it is used by organizations internationally. The objective of this Standard is to give recommendations for information security management for use by those who are responsible for initiating, implementing or maintaining security in their organization. It is intended to provide a common basis for developing organizational security standards and effective security management practice and to provide confidence in inter-organizational dealings. This Standard is complementary to AS/NZS 4444.2:2000, Information security management, Part 2: Specification for information security management systems (redesignated in Amendment 2 as AS/NZS 7799.2:2000) and HB 231:2000, Information security risk management guidelines. As this Standard is reproduced from an International Standard, the following applies: (a) In the source text ‘this International Standard’ should read ‘this Australian/New Zealand Standard’. (b) A full point should be substituted for a comma when referring to a decimal marker. Information is a vital asset in any organization. The protection and security of information is of prime importance to many aspects of an organization’s business. It is therefore important that an organization implements a suitable set of controls and procedures to achieve information security and manages them to retain that level of security once it is achieved. This Standard is intended for use by managers and employees who are responsible for initiating, implementing and maintaining information security within their organization and it may be considered as a basis for developing organizational security standards. A comprehensive set of controls comprising the best information security practices currently in use is provided in this Standard. This guidance is intended to be as comprehensive as possible. It is intended to serve as a single reference point for identifying the range of controls needed for most situations where information systems are used in industry and commerce and can therefore be applied by large, medium and small organizations. With increasing electronic networking between organizations there is a clear benefit in having a common reference document for information security management. It enables mutual trust to be established between networked information systems and trading partners and provides a basis for the management of these systems between users and service providers. Not all the controls described in this Standard will be relevant to every situation. It cannot take account of local environmental or technological constraints, or be present in a form that suits every potential user in an organization. Consequently this Standard might need to be supplemented by further guidance. It can be used as a basis from which, for example, a corporate policy or an inter-company trading agreement can be developed. The guidance and recommendations provided throughout this Standard should not be quoted as if they were specifications. In particular, care should be taken to ensure that claims of compliance are not misleading. It has been assumed in the drafting of this Standard that the execution of its recommendations is entrusted to suitably qualified and experienced people.
mysql 数据库连接报错误：java.sql.SQLException: No suitable driver found for jdbc
weixin_42803504的博客
02-27 7045
mysql 数据库连接报错误：java.sql.SQLException: No suitable driver found for jdbc 解决方法：1、 连接URL格式出现了问题(Connection conn=DriverManager.getConnection(“jdbc:mysql://localhost:3306/XX”,“root”,“XXXX”) 2、驱动字符串出错(com.m...
处理JDBC：java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/DB
鳄鱼杆的博客
04-30 1万+
文章目录前言一、JDBC简介二、JDBC使用以及处理异常的方法1.导入jar包2.JDBC基础操作3、处理异常：No suitable driver found for jdbc:mysql://localhost:3306/DB总结 前言 今天花费一个多小时的事件处理这个问题，最终的处理方法真的是太…棒了，我重开了个项目，建了下模块，结果问题解决了。 本着斩草要除根……咳咳，刨根问底的原则，我决定细查一下这个问题，下面是我得到的结果！ 一、JDBC简介 不说废话，简单来说：   官方定义了的一套操作关
no suitable driver found解决方法
weixin_41691735的博客
06-09 7003
一是：连接URL格式出现了问题(Connection conn=DriverManager.getConnection("jdbc:mysql://localhost:3306/XX","root","XXXX") 二是：驱动字符串出错(com.mysql.jdbc.Driver) 三是Classpath中没有加入合适的mysql_jdbc驱动 ...
已解决No suitable driver found for jdbc:mysql://localhost:3306/ 问题
05-01 4万+
已解决No suitable driver found for jdbc:mysql://localhost:3306/ 问题
No Suitable Driver Found For Jdbc解决方法
热门推荐
一勺菠萝丶的博客
08-21 11万+
在学习java数据库连接池使用的时候遇到问题,无法连接到数据库,之前练习别的时候都没事,莫名的到这里有连接不上了,查看日志是”No Suitable Driver Found For Jdbc”,但查看数据库连接配置没问题啊,后来发现原来是少导入了一个包mysql-connector-java-3.1.14-bin.jar,导入该包,问题解决. 总结一下No Suitable Driver...
No suitable driver的解决方法
qq_41933748的博客
09-02 3万+
 一是：连接URL格式出现了问题(Connection conn=DriverManager.getConnection("jdbc:mysql://localhost:3306/XX","root","XXXX")     二是：驱动字符串出错(com.mysql.jdbc.Driver)     三是Classpath中没有加入合适的mysql_jdbc驱动 四是：也是我的问题，maven一...
服务器出现java.sql.SQLException No suitable driver found for 的.pdf
12-05
服务器出现java.sql.SQLException No suitable driver found for 的
ImpalaJDBC连接所需Jar
11-09
包括 ImpalaJDBC3 ImpalaJDBC4 ImpalaJDBC41 三个版本的ImpalaJDBC连接所需Jar
mysql5.6连接驱动jaf，可处理报错java.sql.SQLException: No suitable driver
02-02
mysql5.6连接驱动jaf，可处理报错java.sql.SQLException: No suitable driver
hive 连接数据库mysql配置问题
manbufenglin的专栏
06-18 578
[root@c167 conf]# hive which: no hbase in (/bin:/usr/bin:/usr/local/rvm/gems/ruby-2.3.8/bin:/usr/local/rvm/gems/ruby-2.3.8@global/bin:/usr/local/rvm/rubies/ruby-2.3.8/bin:/usr/local/sbin:/usr/local/b...
No suitable driver found for jdbc:mysql（计算机学与哲学）
gaoge19861207的专栏
09-27 1398
背景：项目build path里是有Mysql数据库驱动文件的，并且baba项目是已经正常使用很长时间了，但是复制出来一个baba1.1的时候，再次运行jpa框架的时候就报出这样一个错误：No suitable driver found for jdbc:mysql 1：上网搜索了一下，网上说可能是驱动程序与数据库版本不一致，我看了一下，我的项目里的果然是mysql-connector-j
解决 No suitable driver found for jdbc:mysql//localhost:3306/ 问题
weixin_45137562的博客
03-22 1万+
原因 1.URL格式问题 我使用的是mysql数据库，其他数据库的格式可去网上查找 url=jdbc:mysql://localhost:3306/数据库名称?约束 //示例如下： url=jdbc:mysql://localhost:3306/emisdb?userSSL=true&userUnicode=true&characterEncoding=utf-8 2.驱动字符串 以下两个驱动具体区别我不清楚 但是使用一个报错，看编译器是否提示使用另一个 driver=com.mysql.
Hive初始化报错
Qiniin的博客
09-19 1617
hive初始化报错 org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema version. Underlying cause: com.mysql.cj.jdbc.exceptions.CommunicationsException : Communications link failure
no suitable driver found for jdbc:mysql//localhost:3306/..
悠悠余香
10-24 3万+
 出现这样的情况，一般有四种原因： 一：连接URL格式出现了问题(Connection conn=DriverManager.getConnection("jdbc:mysql://localhost:3306/XX","root","XXXX") 二：驱动字符串出错(com.mysql.jdbc.Driver)     三：Classpath中没有加入合适的mysql_jd
No suitable driver found for jdbc:mysql//localhost:3306/,javaweb
03-29
This error message usually occurs when the JDBC driver for MySQL is not found or not properly configured in your Java application. To fix this issue, you need to make sure that you have the correct JDBC driver for MySQL installed and that the driver is included in your application's classpath. Here are some steps you can follow to resolve this issue: 1. Download the JDBC driver for MySQL from the official website: https://dev.mysql.com/downloads/connector/j/ 2. Extract the downloaded ZIP file and copy the JAR file to a folder in your project directory. 3. Add the JDBC driver JAR file to your project's classpath. You can do this by adding the following line to your project's build file (e.g. pom.xml for Maven): <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>8.0.23</version> </dependency> 4. Make sure that you are using the correct JDBC URL for your MySQL database. The format should be like this: jdbc:mysql://localhost:3306/your_database_name Replace "your_database_name" with the actual name of your MySQL database. 5. Check that your MySQL database is running and accessible from your Java application. You can test this by using a MySQL client tool (e.g. MySQL Workbench) to connect to the database using the same credentials that your Java application is using. Once you have verified that the JDBC driver is installed and configured correctly, and that your MySQL database is running and accessible, you should be able to connect to the database from your Java application without any issues.

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值