tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Columns Syntax

PDF
Focus Mode
Font Size
Last updated: 2024-10-09 10:38:07

Feature Overview

The columns syntax is used to query the column information of a table.

Supported Versions

The kernel version should be 3.1.15 or later for TXSQL 8.0.

Applicable Scenarios

It is applicable to scenarios where a lot of column information is queried from a table and the query performance needs improvement.

Use Instructions

List Columns Syntax

A single column is specified:
CREATE TABLE `t1` (
`id` int DEFAULT NULL,
`purchased` varchar(12) DEFAULT NULL,
KEY `idx` (`id`,`purchased`) GLOBAL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
PARTITION BY RANGE (`id`)
SUBPARTITION BY LIST COLUMNS (`purchased`)
SUBPARTITION TEMPLATE
(SUBPARTITION s0 VALUES IN ('0', '1', '2') ENGINE = InnoDB,
SUBPARTITION s1 VALUES IN ('5', '6', '8') ENGINE = InnoDB)
(PARTITION p0 VALUES LESS THAN (1990) ,
PARTITION p1 VALUES LESS THAN (1999));
Multiple columns are specified:
CREATE TABLE `t2` (
`id` int DEFAULT NULL,
`purchased` varchar(12) DEFAULT NULL,
KEY `idx` (`id`,`purchased`) GLOBAL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
PARTITION BY RANGE (`id`)
SUBPARTITION BY LIST COLUMNS (`purchased`, `id`)
SUBPARTITION TEMPLATE
(SUBPARTITION s0 VALUES IN (('0', 1), ('1', 1), ('2', 1995)) ENGINE = InnoDB,
SUBPARTITION s1 VALUES IN (('5' ,5), ('6', 6)) ENGINE = InnoDB)
(PARTITION p0 VALUES LESS THAN (1990) ,
PARTITION p1 VALUES LESS THAN (1999));

Range Columns Syntax

A single column is specified:
CREATE TABLE `t3` (
`id` int DEFAULT NULL,
`purchased` varchar(12) DEFAULT NULL,
KEY `idx` (`id`,`purchased`) GLOBAL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
PARTITION BY RANGE (`id`)
SUBPARTITION BY RANGE COLUMNS (`purchased`)
SUBPARTITION TEMPLATE
(SUBPARTITION s0 VALUES LESS THAN ('5') ENGINE = InnoDB,
SUBPARTITION s1 VALUES LESS THAN ('8') ENGINE = InnoDB)
(PARTITION p0 VALUES LESS THAN (1990) ,
PARTITION p1 VALUES LESS THAN (1999));
Multiple columns are specified:
CREATE TABLE `t4` (
`id` int DEFAULT NULL,
`purchased` varchar(12) DEFAULT NULL,
KEY `idx` (`id`,`purchased`) GLOBAL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
PARTITION BY RANGE (`id`)
SUBPARTITION BY RANGE COLUMNS (`purchased`, `id`)
SUBPARTITION TEMPLATE
(SUBPARTITION s0 VALUES LESS THAN ('5', 55) ENGINE = InnoDB,
SUBPARTITION s1 VALUES LESS THAN ('8', 88) ENGINE = InnoDB)
(PARTITION p0 VALUES LESS THAN (1990) ,
PARTITION p1 VALUES LESS THAN (1999));

Supported Data Types of Columns

For supported data types of columns, see official documentation.

Pruning Instructions

Subpartition pruning and partition pruning use the same method and are independent of each other. Specifically, partition pruning can filter the partition key part in a WHERE condition to obtain a partition set s1, and subpartition pruning can filter the subpartition key part in the WHERE condition to obtain a subpartition template set s2. The final result is that s2 in each s1 is selected.

Restrictions

The new parameter txsql_subpartition_support_multiple_columns restricts the use of multiple columns. When it is set to OFF, only single-column syntax is allowed. When it is set to ON, both multiple-column and single-column syntax are allowed.
Parameter Name
Dynamic
Type
Default Value
Valid Values/Value Range
Description
txsql_subpartition_support_multiple_columns
yes
bool
OFF
OFF/ON
Restricts the use of multiple columns. When it is set to OFF, only single-column syntax is allowed. When it is set to ON, both multiple-column and single-column syntax are allowed.

Help and Support

Was this page helpful?

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

Feedback