Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- Security Orchestration
-
Playbook Overview
- Ransomware Incident Response Solution
- Attack Link Analysis Alert Notification
- HSS Isolation and Killing of Malware
- Automatic Renaming of Alert Names
- Auto High-Risk Vulnerability Notification
- Automatic Notification of High-Risk Alerts
- Auto Blocking for High-risk Alerts
- Real-time Notification of Critical Organization and Management Operations
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- Key Operations Recorded by CTS
-
Best Practices
-
Log Access and Transfer Operation Guide
- Solution Overview
- Resource Planning
- Process Flow
-
Procedure
- (Optional) Step 1: Buy an ECS
- (Optional) Step 2: Buy a Data Disk
- (Optional) Step 3: Attach a Data Disk
- Step 4: Create a Non-administrator IAM User
- Step 5: Configure Network Connection
- Step 6: Install the Component Controller (isap-agent)
- Step 7: Install the Log Collection Component (Logstash)
- (Optional) Step 8: Creating a Log Storage Pipeline
- Step 9: Configure a Connector
- (Optional) Step 10: Configure a Log Parser
- Step 11: Configure a Log Collection Channel
- Step 12: Verify Log Access and Transfer
- Credential Leakage Response Solution
-
Log Access and Transfer Operation Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Alert Management
- Incident Management
- Indicator Management
- Playbook Management
- Alert Rule Management
- Playbook Version Management
- Playbook Rule Management
- Playbook Instance Management
- Playbook Approval Management
- Playbook Action Management
- Incident Relationship Management
- Data Class Management
- Workflow Management
- Data Space Management
- Pipelines
- Workspace Management
- Metering and Billing
- Metric Query
- Baseline Inspection
- Appendix
- FAQs
SELECT
The syntax of a complete analysis statement is as follows:
1 2 3 4 |
SELECT [DISTINCT] (* | expression) [AS alias] [, ...] [GROUP BY expression [, ...] [HAVING predicates]] [ORDER BY expression [ASC | DESC] [, ...]] [LIMIT size OFFSET offset] |
SELECT indicates the field to be queried. The following part describes parameters and examples for the SELECT syntax.
Using * to query all fields.
1 |
SELECT * |
account_number |
firstname |
gender |
city |
balance |
employer |
state |
lastname |
age |
---|---|---|---|---|---|---|---|---|
1 |
Amber |
M |
Brogan |
39225 |
Pyrami |
IL |
Duke |
32 |
16 |
Hattie |
M |
Dante |
5686 |
Netagy |
TN |
Bond |
36 |
13 |
Nanette |
F |
Nogal |
32838 |
Quility |
VA |
Bates |
28 |
18 |
Dale |
M |
Orick |
4180 |
null |
MD |
Adams |
32 |
Querying a Specified Field
1 |
SELECT firstname, lastname |
firstname |
lastname |
---|---|
Amber |
Duke |
Hattie |
Bond |
Nanette |
Bates |
Dale |
Adams |
Using AS to Define Field Aliases
1 |
SELECT account_number AS num |
num |
---|
1 |
16 |
13 |
18 |
Using the DISTINCT Statement
1 |
SELECT DISTINCT age |
age |
---|
32 |
36 |
28 |
Using SQL Functions
For details about functions, see Functions.
1 |
SELECT LENGTH(firstname) as len, firstname |
len |
firstname |
---|---|
4 |
Amber |
6 |
Hattie |
7 |
Nanette |
4 |
Dale |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.