The JSON field type does not have its own index in the current version, so it is very terrible in production. The efficiency of adding, deleting, modifying, and checking JSON fields can be imagined, and it is basically unusable. Maybe it is based on this. MySQL5.7 provides a Generated field type, which is called generated column or calculated column on the Internet. Let’s first understand what Generated Column is.
1. Introduction to Generated Column
Generated Column is a new feature introduced in MySQL 5.7.6. The so-called Centerated Column means that this column in the database is calculated from other columns. To illustrate, quote the example in the official reference manual:
CREATE TABLE triangle ( sidea DOUBLE, sideb DOUBLE, sidec DOUBLE AS (SQRT(sidea * sidea + sideb * sideb)) ); INSERT INTO triangle (sidea, sideb) VALUES(1,1),(3,4),(6,8); mysql> SELECT * FROM triangle; +-------+-------+--------------------+ | sidea | sideb | sidec | +-------+-------+--------------------+ | 1 | 1 | 1.4142135623730951 | | 3 | 4 | 5 | | 6 | 8 | 10 | +-------+-------+--------------------+
There are two types of Generated Column, namely Virtual Generated Column and Stored Generated Column. The former only saves Generated Column in the data dictionary (metadata of the table), and This column of data will not be persisted to disk; the latter will persist the Generated Column to disk instead of calculating it each time it is read. Obviously, the latter stores data that can be calculated from existing data, requires more disk space, and has no advantage over Virtual Column. Therefore, in MySQL 5.7, the type of Generated Column is not specified, and the default is Virtual Column. Although Virtal Generated Column should generally be used, there are currently many restrictions on using Virtual Generated Column: it cannot be used as a primary key, cannot be used as a primary key, cannot create full-text indexes and spatial indexes, etc., but it may be supported in subsequent versions. Therefore, if you use Generated Column fields for indexing, you should use Stored Generated Column. When using Generated Column for indexing, the official solution for JSON field indexing is to use Stored Generated Column. The table creation statement using Stored Generated Column is as follows, just adding a word:
CREATE TABLE triangle ( sidea DOUBLE, sideb DOUBLE, sidec DOUBLE AS (SQRT(sidea * sidea + sideb * sideb) STORED) );
2. Notes on Generated Column
Generated Column cannot be written, it is automatically generated; When creating, you must consider whether the calculation formula of this column is reasonable. If it is unreasonable, no error will be reported when creating it, but an error will be reported when inserting a value when using it. The columns that Generated Column depends on will prompt an error when deleting, and Generated Column must be deleted first. Only then can we delete the columns it depends on; the definition of Generated Column is illegal. For example, if we define generated column as "column x + column y", it is obvious that column x or column y are both numerical. If we define column x or column y If the column is defined (or modified) as character type, an error is expected, but in fact we can create it normally, but an error will be reported when inserting.
3. Use Generated Column to add an index to the JSON field
Normally, the query related to the JSON field scans the entire table, because the JSON field itself If the index cannot be created, we use the Generated Column feature to generate columns for the relevant keys in the JSON field as Generated Column, and then index the Generated Column:
ALTER TABLE json_test ADD COLUMN age INT AS (JSON_EXTRACT(user_info,'$.age')) STORED, ADD KEY idx_age (age);
The before and after comparison is as follows:
#It can be clearly seen that after using Generated Column and adding an index, the index is used to query the value in the JSON field.
Conclusion
The emergence of Generated Column and JSON Column in MySQL5.7 makes it possible to replace NoSQL such as MongoDB in some scenarios, although overall it has not been done by MongoDB and others. is so powerful, but I believe that there will be more and more scenarios in which these two types are used in the future. At the same time, the challenges to DBA will also become greater and greater. It is hoped that intensive use of JSON type business will be run using independent MySQL instances to prevent JSON from becoming a large field. (The size of the JSON column stored in the JSON document is limited to the value of the max_allowed_packet system variable) This has an impact on other operations.
The above is the content of MySQL 5.7 new features | Json Column and Generated Column (Part 2). For more related content, please pay attention to the PHP Chinese website (www.php.cn)!

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

Zend Studio 13.0.1
Powerful PHP integrated development environment
