tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

JSON Function

PDF
Focus Mode
Font Size
Last updated: 2025-05-09 11:51:19
In 2.2410.x and later versions, the read-only analysis engine adds support for JSON (JavaScript Object Notation) data types that conform to RFC 7159 standard. Users can save semi-structured JSON data and can access and modify data in JSON documents.
JSON documents stored in JSON columns can be converted into a format that is easy to read and access. When the server needs to read a JSON value stored in binary format, it does not need to parse the value from text.
Besides JSON data types, there is a set of SQL functions that can be used to create, search, and perform other operations on JSON values. The supported functions are as follows:

JSON_OBJECT Function

Create a JSON object.
Syntax: JSON_OBJECT(key1, value1, key2, value2…)
Create a JSON object based on the input parameter value.

JSON_REMOVE Function

Delete the corresponding path from the specified JSON object.
Syntax: JSON_REMOVE(json_doc, path[, path] ...)
json_doc is a JSON field, and path is a path. Multiple paths are supported.

JSON_EXTRACT Function

Extract elements at the specified path from a JSON field. If the specified path does not exist, NULL is returned. Multiple paths can be specified, and multiple matched values will be returned as an array.
Syntax: JSON_EXTRACT(json_doc, path[, path] ...) is synonymous with column-> path.
json_doc is a JSON field, and path is a path.

JSON_UNQUOTE Function

Escape JSON and output it as a string.
Syntax: JSON_UNQUOTE(column -> path) is synonymous with column->> path.
json_doc is a JSON field, and path is a path.

JSON_CONTAINS Function

Specify whether the path contains the specified data. If it does, 1 is returned; if not, 0 is returned. If any parameter is NULL or the path does not exist, NULL is returned.
Syntax: JSON_CONTAINS(json_doc, candidate[, path])
json_doc is a JSON field, candidate is a judgment value, and path is a path.

JSON_CONTAINS_PATH Function

Check whether a specified path exists and whether one or all conditions are met. If it exists, 1 is returned; if not, 0 is returned. If any parameter is NULL, NULL is returned.
Syntax: JSON_CONTAINS_PATH(json_doc, one_or_all, path[, path] …)
json_doc is a JSON field. In one_or_all, one means return once one is queried, and all means return after all are queried. path is a path. Multiple paths are supported.

Type Conversion

Support conversion from JSON to INT, UINT, FLOAT, STRING, DATE, DATETIME, and DURATION.
Support conversion from INT, UINT, FLOAT, STRING, DATE, DATETIME, and DURATION to JSON.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback