Mysql 设置问题,当使用一些开源的软件动态安装MYSQL数据库后,发现里面的中文全是乱码。...
Mysql 安装OK。
使用开源软件安装Mysql数据库。数据库的编码正确,但录入的数据或是设计表的说明中的中文成乱码。
修改方案:
在my.ini 添加如下设置。
[mysqld]
character-set-server=utf8
[mysql]
default-character-set=utf8
character_set_server = utf8
备份一个可用的my.ini
# Other default tuning values # MySQL Server Instance Configuration File # ---------------------------------------------------------------------- # Generated by the MySQL Server Instance Configuration Wizard # # # Installation Instructions # ---------------------------------------------------------------------- # # On Linux you can copy this file to /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options # (@localstatedir@ for this installation) or to # ~/.my.cnf to set user-specific options. # # On Windows you should keep this file in the installation directory # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To # make sure the server reads the config file use the startup option # "--defaults-file". # # To run the server from the command line, execute this in a # command line shell, e.g. # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # To install the server as a Windows service manually, execute this in a # command line shell, e.g. # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # And then execute this in a command line shell to start the server, e.g. # net start MySQLXY # # # Guidelines for editing this file # ---------------------------------------------------------------------- # # In this file, you can use all long options that the program supports. # If you want to know the options a program supports, start the program # with the "--help" option. # # More detailed information about the individual options can also be # found in the manual. # # For advice on how to change settings please see # https://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html # # # CLIENT SECTION # ---------------------------------------------------------------------- # # The following options will be read by MySQL client applications. # Note that only client applications shipped by MySQL are guaranteed # to read this section. If you want your own MySQL client program to # honor these values, you need to specify it as an option during the # MySQL client library initialization. # [client]# pipe=# socket=MYSQLport=3306[mysql] no-beep default-character-set=utf8 character_set_server = utf8# default-character-set=# SERVER SECTION # ---------------------------------------------------------------------- # # The following options will be read by the MySQL Server. Make sure that # you have installed the server correctly (see above) so it reads this # file. # # server_type=3 [mysqld]character-set-server=utf8# The next three options are mutually exclusive to SERVER_PORT below. # skip-networking # enable-named-pipe # shared-memory# shared-memory-base-name=MYSQL# The Pipe the MySQL Server will use # socket=MYSQL# The TCP/IP Port the MySQL Server will listen on port=3306# Path to installation directory. All paths are usually resolved relative to this. # basedir="C:/Program Files/MySQL/MySQL Server 5.7/"# Path to the database root datadir=C:/ProgramData/MySQL/MySQL Server 5.7/Data# The default character set that will be used when a new schema or table is # created and no character set is defined # character-set-server=# The default storage engine that will be used when create new tables when default-storage-engine=INNODB# Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"# General and Slow logging. log-output=FILEgeneral-log=0general_log_file="iZfjm93d732effZ.log"slow-query-log=1slow_query_log_file="iZfjm93d732effZ-slow.log"long_query_time=10# Error Logging. log-error="iZfjm93d732effZ.err"# ***** Group Replication Related ***** # Specifies the base name to use for binary log files. With binary logging # enabled, the server logs all statements that change data to the binary # log, which is used for backup and replication. # log-bin# ***** Group Replication Related ***** # Sets the binary logging format, and can be any one of STATEMENT, ROW, # or MIXED. ROW is suggested for Group Replication. # binlog_format# ***** Group Replication Related ***** # Causes the master to write a checksum for each event in the binary log. # binlog_checksum supports the values NONE (disabled) and CRC32. # The default is CRC32. When disabled (value NONE), the server verifies # that it is writing only complete events to the binary log by writing # and checking the event length (rather than a checksum) for each event. # NONE must be used with Group Replication. # binlog_checksum# ***** Group Replication Related ***** # The base name for the relay log. The server creates relay log files in # sequence by adding a numeric suffix to the base name. If you specify this # option, the value specified is also used as the base name for the relay log # index file. Relay logs increase speed by using load-balancing between disks. relay_log="iZfjm93d732effZ-relay"# ***** Group Replication Related ***** # Specifies the server ID. For servers that are used in a replication topology, # you must specify a unique server ID for each replication server, in the # range from 1 to 2^32 − 1. “Unique” means that each ID must be different # from every other ID in use by any other replication master or slave. server-id=1 # ***** Group Replication Related ***** # The host name or IP address of the slave to be reported to the master # during slave registration. This value appears in the output of SHOW SLAVE HOSTS # on the master server. Leave the value unset if you do not want the slave to # register itself with the master. # report_host=0.0# ***** Group Replication Related ***** # The TCP/IP port number for connecting to the slave, to be reported to the master during # slave registration. Set this only if the slave is listening on a nondefault port or if # you have a special tunnel from the master or other clients to the slave. report_port=3306# ***** Group Replication Related ***** # This option specifies whether global transaction identifiers (GTIDs) are # used to identify transactions. ON must be used with Group Replication. # gtid_mode# ***** Group Replication Related ***** # When enabled, the server enforces GTID consistency by allowing execution of # only statements that can be safely logged using a GTID. You must set this # option to ON before enabling GTID based replication. # enforce_gtid_consistency# ***** Group Replication Related ***** # Whether updates received by a slave server from a master server should be # logged to the slave's own binary log. Binary logging must be enabled on # the slave for this variable to have any effect. ON must be used with # Group Replication. # log_slave_updates# ***** Group Replication Related ***** # Determines whether the slave server logs master status and connection information # to an InnoDB table in the mysql database, or to a file in the data directory. # The TABLE setting is required when multiple replication channels are configured. # master_info_repository# ***** Group Replication Related ***** # Determines whether the slave server logs its position in the relay logs to an InnoDB # table in the mysql database, or to a file in the data directory. The TABLE setting is # required when multiple replication channels are configured. # relay_log_info_repository# ***** Group Replication Related ***** # Defines the algorithm used to hash the writes extracted during a transaction. If you # are using Group Replication, this variable must be set to XXHASH64 because the process # of extracting the writes from a transaction is required for conflict detection on all # group members. # transaction_write_set_extraction lower_case_table_names=1# Secure File Priv. secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"# The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=151# The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_open_cache=2000# Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=59M# How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=10#*** MyISAM Specific options # The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G# If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=109M# Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=8M# Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=64Kread_rnd_buffer_size=256K#*** INNODB Specific options *** # innodb_data_home_dir=# Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. # skip-innodb# If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. innodb_flush_log_at_trx_commit=1# The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=1M# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system. Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. innodb_buffer_pool_size=8M# Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. innodb_log_file_size=48M# Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=8# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full. innodb_autoextend_increment=64# The number of regions that the InnoDB buffer pool is divided into. # For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, # by reducing contention as different threads read and write to cached pages. innodb_buffer_pool_instances=8# Determines the number of threads that can enter InnoDB concurrently. innodb_concurrency_tickets=5000# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before # it can be moved to the new sublist. innodb_old_blocks_time=1000# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10. innodb_open_files=300# When this variable is enabled, InnoDB updates statistics during metadata statements. innodb_stats_on_metadata=0# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table # in a separate .ibd file, rather than in the system tablespace. innodb_file_per_table=1# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none. innodb_checksum_algorithm=0# The number of outstanding connection requests MySQL can have. # This option is useful when the main MySQL thread gets many connection requests in a very short time. # It then takes some time (although very little) for the main thread to check the connection and start a new thread. # The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily # stops answering new requests. # You need to increase this only if you expect a large number of connections in a short period of time. back_log=80# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and # synchronize unflushed data to disk. # This option is best used only on systems with minimal resources. flush_time=0# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use # indexes and thus perform full table scans. join_buffer_size=256K# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the # mysql_stmt_send_long_data() C API function. max_allowed_packet=4M# If more than this many successive connection requests from a host are interrupted without a successful connection, # the server blocks that host from performing further connections. max_connect_errors=100# Changes the number of file descriptors available to mysqld. # You should try increasing the value of this option if mysqld gives you the error "Too many open files". open_files_limit=4161# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the # sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization # or improved indexing. sort_buffer_size=256K# The number of table definitions (from .frm files) that can be stored in the definition cache. # If you use a large number of tables, you can create a large table definition cache to speed up opening of tables. # The table definition cache takes less space and does not use file descriptors, unlike the normal table cache. # The minimum and default values are both 400. table_definition_cache=1400# Specify the maximum size of a row-based binary log event, in bytes. # Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256. binlog_row_event_max_size=8K# If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk. # (using fdatasync()) after every sync_master_info events. sync_master_info=10000# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk. # (using fdatasync()) after every sync_relay_log writes to the relay log. sync_relay_log=10000# If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk. # (using fdatasync()) after every sync_relay_log_info transactions. sync_relay_log_info=10000# Load mysql plugins at start."plugin_x ; plugin_y". # plugin_load# The TCP/IP Port the MySQL Server X Protocol will listen on. # loose_mysqlx_port=33060
转载于:https://www.cnblogs.com/challengesoflife/p/11149446.html
Mysql 设置问题,当使用一些开源的软件动态安装MYSQL数据库后,发现里面的中文全是乱码。...相关推荐
- liunx上mysql源码安装mysql,搞定linux上MySQL编程(一):linux上源码安装MySQL
[版权声明:尊重原创,转载请保留出处:blog.csdn.net/shallnet,文章仅供学习交流,请勿用于商业用途] 1. 首先下载源码包: ftp://ftp.jaist.ac.jp/pub/m ...
- 树莓派要mysql的密码_树莓派raspberry Pi 3B+系统中安装mysql过程中不提示输入密码,安装完后如何设置密码...
树莓派raspberry Pi 3B+安装mysql未提示输入密码,安装后修改mysql密码默认密码 使用mysql -uroot -p 命令连接mysql时,报错 pi@raspberrypi:/ ...
- mysql下载64位 linux_在linux(CentOS-6.7_x86_64)上安装mysql成功记录
查看linux服务器的yum源设置: [root@hadoop03 yum.repos.d]#cd /etc/yum.repos.d [root@hadoop03 yum.repos.d]#ll to ...
- MySQL--入门篇:MySQL入门必会知识 Windows安装MySQL的zip包 一步一步带你图解安装MySQL过程 详细图解MySQL语句
阅读目录 数据和数据库 MySQL介绍 MySQL的详细安装教程 Windows版本:MySQLl的安装.启动和基础配置 下载 配置 环境变量 安装 和 启动MySQL服务端 MySQL的卸载 MyS ...
- mysql ver 14.14 distrib 5.5.49_MySQL简介及安装 mysql Ver 14.14 Distrib 5.7.28
1.MySQL简介 1.数据库产品演变 第一代数据库架构: RDBMS 关系型数据库时代 : 合的时代 代表产品 :Oracle .MSSQL .MySQL.SQL server 第二代数据库架构:拆 ...
- mysql用macbookair,Macbook air OS X Yosemite10.10.5安装MYSQL
记录下折腾了一天终于把MYSQL给装了,坎坷啊! 安装环境: 系统:Macbook air OS X Yosemite10.10.5 软件:mysql-5.6.27-osx10.9-x86_64.dm ...
- 开源资产管理软件-GLPI安装
系统版本 CentOS Linux release 7.5.1804 (Core) 内核 3.10.0-862.el7.x86_64 MySQL MySQL5.7 第一步:关闭selinux和fire ...
- mysql设置主键约束为降序_MySQL约束的概述 - osc_tko37abm的个人空间 - OSCHINA - 中文开源技术交流社区...
MySQL约束 今日学习内容 1.DQL:查询语句 1.排序查询 2.聚合函数 3.分组查询 4.分页查询 2.约束 3.多表关系 4.范式 5.数据库备份和还原 DQL查询语句 排序 通过ORDER ...
- mysql设置停止二进制文件的操作_window下使用二进制文件对mysql数据库备份及恢复(再现用户操作)...
1,查看二进制日志文件是否启用 mysql>show variables like 'log_bin'; 如果未启用,则启用二进制文件(默认是关闭的 ) 2,在mysql的配置文件[mysqld ...
- mysql设置用户永不过期_在Navicat Premium中管理MySQL用户 - 第2部分:创建新用户
第2部分:创建新用户 在第1部分中,我们学习了如何使用Navicat Premium用户管理工具保护MySQL root帐户.本篇文章将讨论设置新用户的帐户详细信息,帐户限制和SSL设置. The G ...
最新文章
- python反转字符串(简单方法)及简单的文件操作示例
- UIButton 按钮控件-IOS开发 (实例)
- 利用NLTK进行分句分词
- GitLab 服务器的迁移以及注意点
- 计算机在材料中的运用结课,计算机在材料科学工程中的应用的结课论文.doc
- SpringBoot 扫描包
- Problem B: 求各位数字之和
- 渗透测试web未设置http头 Strict Transport Security
- 《中国人工智能学会通讯》——11.28 统一先验建模框架 II:整数规划
- 苹果手机软件升级密码_拥有苹果全家桶以后那些事
- Tyvj P1065 津津的储蓄计划
- 计算机趣味知识竞赛策划,大学生趣味知识竞赛活动的策划书
- 如何给PDF加水印?PDF加水印教程
- Linux 下sha1加密
- Azure云服务器搭建
- 历史上最有名的五句农民起义军口号
- 教你怎么筛选排除百度搜索引擎的屏蔽违规词
- 如何用Python编写一个求 1到n阶乘之和的程序
- 私域认知篇:私域流量到底是什么?私域流量现象,私域流量可以解决什么问题,如何开展私域流量?...
- 优雅编程之这样使用枚举和注解,你就“正常”了(二十九)
热门文章
- python 求解给定字符串中的最长DNA序列长度
- 决用 Anaconda 完美解 Python2 和 python3 共存问题
- Python读取文件时出现UnicodeDecodeError: ‘gbk‘ codec can‘t decode byte 0x80 in position ...
- 2021-08-13servlet 原理及注意事项
- r语言 小树转化百分数_魅力语言小课堂|绕口令《说日》
- Android广播时间——实现强制下线功能
- 我喜欢用计算机400字,我喜欢电脑画画作文400字
- java多线程-线程生命周期及状态
- vue基础之组件(创建,data,切换,父子以及同级之间的传值,插槽solt)
- 二十五、JAVA多线程(二、吃苹果案例)