MYSQL连接时一直提示字符集错误，发现源码中存在一个小BUG......
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
由于mysql和oracle编码集定义不一致，猜测是为了方便省事页面上是写死的，但是源码中相关的判断语句并未保持同步，需要调换图2中的“iso-8859-1”和“latin1”的位置顺序，不然这个三目运算是没有意义的。。。会持续报错。。。(也不能怪阿里的同学，甲骨文也挺操蛋的，既然都是自己的产品了，编码集定义应该统一下的。。。)但是这里显然是不影响程序运行的，影响首次搭建试用的同学的心情。。。希望下次更新的时候能够修复这个BUG咯
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the charset judgment shown in the second screenshot and compare its handling of “iso-8859-1” and “latin1”. Confirm the ordering makes the conditional meaningful, then verify that a MySQL connection no longer repeatedly reports the charset error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100