Why should mysql specify encoding when creating a database

This article mainly introduces "Why should mysql specify a code when creating a database". In daily operation, I believe that many people have doubts about why they should specify a code when creating a database by mysql. The editor consulted all kinds of materials and sorted out a simple and easy-to-use method of operation. I hope it will be helpful to answer the question of "why should you specify a code when mysql creates a database?" Next, please follow the editor to study!

It is important for mysql to specify a code when creating a database, and many developers use the default code, but from my experience, coding a database can largely avoid garbled problems caused by inverted exports.

The standard we follow is that the coding of databases, tables, fields and pages or text should be unified.

Many mysql database tools (except phpmyadmin, which I use occasionally, are powerful and slow) do not support specifying the database encoding at creation time. Of course, you can change my.ini to solve this problem, but you need to restart mysql, but it will be more effective to use the following statement

GBK: create database test2 DEFAULT CHARACTER SET gbk COLLATE gbk_chinese_ci

UTF8: CREATE DATABASE `test2` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci

At this point, the study on "Why should mysql specify a code when creating a database" is over. I hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!