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

Description of Supported Logical Operations

PDF
Focus Mode
Font Size
Last updated: 2025-05-09 11:51:18
The read-only analysis engine currently supports most MySQL logical operations, but there are still limitations and incompatibilities in some scenarios. This document introduces the support for logical operations in the read-only analysis engine and lists the type limitations in input parameters. Input parameters and usage methods not mentioned in the document are not supported.

Supported Logical Operations

and Operation

Syntax: op1 and op2
Supported value types for op1: Only the bool data type is supported.
Supported value types for op2: Only the bool data type is supported.

or Operation

Syntax: op1 or op2
Supported value types for op1: Only the bool data type is supported.
Supported value types for op2: Only the bool data type is supported.

not Operation

Syntax: not op1
Supported value types for op1: Only the bool data type is supported.

case Operation

Syntax: case when search_condition then statement_list else statement_list end
Supported value types for search_condition: Only the bool data type is supported.
Supported value types for statement_list: int, bigint, double, decimal, varchar, and char.

if Operation

Syntax: if(expr1,expr2,expr3)
Supported value types for expr1: Only the bool data type is supported.
Supported value types for expr2: int, bigint, double, decimal, varchar, and char.
Supported value types for expr3: int, bigint, double, decimal, varchar, and char.

ifnull Operation

Syntax: ifnull(expr1, expr2)
Supported value types for expr1: int, bigint, double, decimal, varchar, and char.
Supported value types for expr2: int, bigint, double, decimal, varchar, and char.

isnull Operation

Syntax: isnull(expr1)
Supported value types for expr1: int, bigint, double, decimal, varchar, and char.

in Operation

Syntax: expr IN (value,...)
Supported value types for expr: int, bigint, double, decimal, varchar, and char.
Supported value types for value: int, bigint, double, decimal, varchar, and char.
Note:
In scenarios with multiple value values, the value should be a constant and cannot be a variable or field name. For example, it can only be used in the format of column in ('1','2','3') rather than columnA in (columnB,varA).
Syntax: expr IN (sub_query)
Supported value types for expr: int, bigint, double, decimal, varchar, and char.
Supported value types for sub_query: Subquery and single field.

like Operation

Syntax: expr like pattern
Supported value types for expr: int, bigint, double, decimal, varchar, and char.
Supported value types for pattern: int, bigint, double, decimal, varchar, and char.
Note:
The pattern only supports constants and does not support the substitution of variables or field names.

Coalescence Operation

Syntax: coalesce(value,...)
Supported value types for value: int, bigint, double, decimal, varchar, and char.

Help and Support

Was this page helpful?

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

Feedback