How can we become familiar with mysql?

Recently I have been looking at php recruitment, and I will almost mention 'familiar with mysql'. What knowledge points should I master before I can confidently say that I am familiar with mysql? I entered the line for nearly three years, but mysql is still stuck in simple addition, query, modification, and work-related projects, the traffic is not high, so I didn't go deep into mysql, fine... recently I have been looking at php recruitment, and I will almost mention 'familiar with mysql'. What knowledge points should I master before I can confidently say that I am familiar with mysql?
I have been in mysql for nearly three years, but mysql is still stuck in simple addition, deletion, query, modification, and work-related projects, and the traffic is not high, so I didn't go deep into mysql, all energy is spent on the php business logic.
Therefore, I would like to ask you what books I have to read or what knowledge I know can be called 'familiar with mysql'

Reply content:

Recently I have been looking at php recruitment, and I will almost mention 'familiar with mysql'. What knowledge points should I master before I can confidently say that I am familiar with mysql?
I have been in mysql for nearly three years, but mysql is still stuck in simple addition, deletion, query, modification, and work-related projects, and the traffic is not high, so I didn't go deep into mysql, all energy is spent on the php business logic.
Therefore, I would like to ask you what books I have to read or what knowledge I know can be called 'familiar with mysql'

I am not familiar with mysql, but I feel that the following requirements must be met to my degree of familiarity:

1. Familiar with all mysql-specific SQL statements and data types. For example, mysql uses limit for paging and corresponding oracle uses rownum. You cannot write an SQL statement and google it.

2. Be familiar with mysql 80% configurations, including the configuration data tables and configuration files in the mysql database. be familiar with these configurations to solve those problems.

3. Mysql deployment, master-slave, master-slave

4. Some limitations or features of native mysql are worth the experience .. For example, the size of a single instance should not exceed 150 GB, and the number of rows of data tables with fields should not exceed 5 million.

Proficient in:

1. Familiar with all mysql configurations, including database configurations and configuration files, and able to make specific optimizations for different deployment environments, including performance and security

2. I started to study the source code and introduced some features from the source code level.

3. To solve a problem, at least know where the source code can be modified.

4. Provide the most reasonable design for business needs and mysql features

All of the above are I boast about X, and I am not familiar with it myself. It is for reference only.

From the perspective of db analytics, there are also DBAs, and so on. From performance-based design, you can design your methods and structures, you will naturally go into your sytax and function usage
But usually you don't want to be a trusted DBA. You don't have time to write a program. This is a very powerful role.
Or your company is willing to give you two tickets LOL