@clickzetta/cz-cli-darwin-arm64 0.5.16 → 0.5.17

package/bin/skills/lakehouse-doc-en/references/quick_start_workspace_user.md

@@ -18,31 +18,31 @@ Before reading this guide, it is recommended to first read and understand the fo
 
 ## Operation Guide
 
-1. As shown below, click the button to enter the Lakehouse service instance:
+1. click the button to enter the Lakehouse service instance:
+
 
-   ![](.topwrite/assets/image_1747991184372.png)
 
 2. Navigate to "Management > Workspace" page
 
-   ![](.topwrite/assets/image_1747991595948.png)
+
 
 3. Click the workspace name to enter the details page. On this page, you can see the existing member users and defined roles under the workspace. The workspace creator is added as a member by default and granted the `workspace_admin` role.
 
-   ![](.topwrite/assets/image_1747991623831.png)
+
 
 4. Click "Add User" and select existing users to join the workspace. If the user has not been created yet, you can refer to this document to create a user first before adding: [Getting Started: How to Quickly Add and Manage Users](quick_start_user_management.md)
 
-5. After selecting a user, to ensure the user has the necessary permissions to use features, it is recommended to use the "Add User and Grant Role" operation option:
+5. After selecting a user, to ensure the user has the necessary permissions to use features, it is recommended to use the "Add User and Grant Role" operation option.
+
 
-   ![](.topwrite/assets/image_1747991688907.png)
 
 6. Select the appropriate role based on the interface description. If you want the user to be able to develop and run tasks within the workspace, it is recommended to assign the `workspace_dev` role. Click "Grant Role" or the corresponding button to complete the entire add and authorization process.
 
-   ![](.topwrite/assets/image_1747991697185.png)
+
 
 7. On the workspace details page, you can view the user just added and the role granted.
 
-   ![](.topwrite/assets/image_1747991704056.png)
+
 
 ## Limitations
 

package/bin/skills/lakehouse-doc-en/references/quickstart.md

@@ -1,21 +1,24 @@
 # AI Gateway Quick Start
 
-This section guides you through the complete initial setup of Singdata AI Gateway in **10 minutes** — from logging into the platform to successfully calling your first large model API. By the end of this section, you will have mastered the core basic operations of the product and be able to quickly integrate AI capabilities into your business systems.
+This section guides you through the complete initial setup of AI Gateway in **10 minutes** — from logging into the platform to successfully calling your first large model API.
 
-### 1 Prerequisites
+---
 
-Before you start using Singdata AI Gateway, make sure you have completed the following preparations:
+## Prerequisites
+
+Before you start using AI Gateway, make sure you have completed the following preparations:
 
 1. You have a Singdata platform enterprise account (personal accounts cannot use the enterprise-grade AI Gateway service)
 2. You have completed enterprise real-name verification
 3. You have activated the AI Gateway service
 
+---
 
-### 2 Log In to the Singdata Console
+## Log In to the Singdata Console
 
 1. Open a browser and visit the Singdata platform official website:
 
-   * Production address: <https://singdata.com/>
+   - Production address: <https://singdata.com/>
 
 2. Click the **Login** button in the upper-right corner of the page
 
@@ -23,111 +26,113 @@ Before you start using Singdata AI Gateway, make sure you have completed the fol
 
 4. After a successful login, the system will automatically redirect you to the **Singdata platform account home page**
 
-![](/.topwrite/assets/screenshot-20260525-221156.png)
+![](.topwrite/assets/screenshot-20260525-221156.png)
+
+---
 
+## Create Your First API Key
 
-### 3 Create Your First API Key
+An API Key is the unique identity credential for calling AI Gateway services. All model invocation requests must carry a valid API Key for authentication.
 
-An API Key is the unique identity credential for calling Singdata AI Gateway services. All model invocation requests must carry a valid API Key for authentication.
+1. On the Singdata platform account home page, find the **AI Gateway** service card and click it to enter the product page
 
-1. On the Singdata platform account home page, find the **"AI Gateway"** service card and click it to enter the product page
+2. After entering the AI Gateway product interface, the system displays the **API KEY Management** page by default
 
-2. After entering the AI Gateway product interface, the system displays the **"API KEY Management"** page by default
+3. Click the **New** button in the upper-right corner of the page
 
-3. Click the **"New"** button in the upper-right corner of the page
+4. In the **New API KEY** dialog that appears, fill in the following information:
 
-4. In the **"New API KEY"** dialog that appears, fill in the following information:
+   - **Name**: Enter an identifying name for the API Key. The recommended naming convention is "business line - environment - purpose", for example "Customer Service - Production - General Chat"
 
-   * **Name**: Enter an identifying name for the API Key. The recommended naming convention is "business line - environment - purpose", for example "Customer Service - Production - General Chat"
+   - **Quota period**: Select the reset cycle for the Token quota from the dropdown menu. Four options are supported:
 
-   * **Quota period**: Select the reset cycle for the Token quota from the dropdown menu. Four options are supported:
+     - Day: Token quota resets automatically at midnight every day
+     - Natural week: Token quota resets automatically at midnight every Monday
+     - Month: Token quota resets automatically at midnight on the 1st of each month
+     - Long-term: Token quota is permanently valid and will not reset automatically; it is consumed until exhausted
 
-     * Day: Token quota resets automatically at midnight every day
-     * Natural week: Token quota resets automatically at midnight every Monday
-     * Month: Token quota resets automatically at midnight on the 1st of each month
-     * Long-term: Token quota is permanently valid and will not reset automatically; it is consumed until exhausted
+   - **Token quota**: Enter the maximum number of tokens allowed to be consumed within the period
 
-   * **Token quota**: Enter the maximum number of tokens allowed to be consumed within the period
+5. After confirming the information is correct, click the **Confirm** button in the lower-right corner of the dialog
 
-4. After confirming the information is correct, click the **"Confirm"** button in the lower-right corner of the dialog
+6. The system will automatically generate the API Key and display it in the list. Click the **eye icon** in the API Key column to view the full key string
 
-5. The system will automatically generate the API Key and display it in the list. Click the **eye icon** in the API Key column to view the full key string
+> ⚠️ **Note**: Never share your API Key with others, and do not hard-code it in source code or commit it to a public repository. If you discover that an API Key has been leaked, immediately revoke it in the console and generate a new one.
 
-> ⚠️ **Note:**
->
-> * Never share your API Key with others, and do not hard-code it in source code or commit it to a public repository
-> * If you discover that an API Key has been leaked, immediately revoke it in the console and generate a new one
+![](.topwrite/assets/2.jpeg)
 
-![](/.topwrite/assets/2.jpeg)
+---
 
-### 4 Configure a Routing Policy (Optional)
+## Configure a Routing Policy (Optional)
 
 The routing policy determines which models your API Key can call and the priority order for model invocation. By default, a newly created API Key can call all built-in models provided by the platform and uses a "price priority" sorting strategy.
 
 If you need to use a custom routing policy or BYOK models, follow these steps:
 
 1. In the API Key list, find the API Key you just created
-2. Click the **"Routing Policy"** button in the actions column
-3. In the **"Routing Policy Configuration"** dialog that appears, you can configure the following:
+2. Click the **Routing Policy** button in the actions column
+3. In the **Routing Policy Configuration** dialog that appears, you can configure the following:
 
-#### Option A: Use Platform Built-in Models (Default)
+### Option A: Use Platform Built-in Models (Default)
 
-* **Provider scope**:
+- **Provider scope**:
 
-  * All providers (default): you can use all built-in models provided by the platform
-  * Select specific providers: check the providers you need; only models from those providers will be available
+  - All providers (default): you can use all built-in models provided by the platform
+  - Select specific providers: check the providers you need; only models from those providers will be available
 
-* **Provider sorting strategy**:
+- **Provider sorting strategy**:
 
-  * Price priority: preferentially calls the lowest-priced available provider
-  * Throughput priority: preferentially calls the highest-throughput available provider
-  * Latency priority: preferentially calls the lowest-latency available provider
+  - Price priority: preferentially calls the lowest-priced available provider
+  - Throughput priority: preferentially calls the highest-throughput available provider
+  - Latency priority: preferentially calls the lowest-latency available provider
 
-![](/.topwrite/assets/3.png)
+![](.topwrite/assets/3.png)
 
-#### Option B: Use Only Your Own BYOK Models
+### Option B: Use Only Your Own BYOK Models
 
-* Check the **"Use my BYOK Key only"** checkbox
-* Select the BYOK Key you have already created from the dropdown list (if you have not created a BYOK Key yet, refer to section 3.3 first)
-* Once checked, this API Key can only call the BYOK models you have bound, and billing will go directly through your own provider account
+- Check the **Use my BYOK Key only** checkbox
+- Select the BYOK Key you have already created from the dropdown list (if you have not created a BYOK Key yet, refer to the relevant documentation first)
+- Once checked, this API Key can only call the BYOK models you have bound, and billing will go directly through your own provider account
 
-4. After completing the configuration, click the **"Save"** button in the lower-right corner of the dialog
+4. After completing the configuration, click the **Save** button in the lower-right corner of the dialog
 
-![](/.topwrite/assets/1.jpeg)
+![](.topwrite/assets/1.jpeg)
 
-### 5 Test a Model Call
+---
+
+## Test a Model Call
 
 After completing the above configuration, you can use the API Key you created to call large model APIs. You can use an OpenAI or Anthropic compatible client or SDK depending on the model you choose.
 
 Using Qwen3.6 Plus as an example, here are the two most common calling methods:
 
-#### Method 1: Call using curl with OpenAI format
+### Method 1: Call using curl
 
 Open a terminal and run the following curl command, replacing `YOUR_API_KEY` with your actual API Key:
 
 ```bash
 curl -X POST https://cn-shanghai-alicloud-aimesh.api.singdata.com/gateway/v1/chat/completions \
--H "Authorization: Bearer $API_KEY" \
--H "Content-Type: application/json" \
--d '{
+  -H "Authorization: Bearer $API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
     "model": "qwen/qwen3.6-plus",
     "messages": [{"role":"user","content":"hello"}]
-}'
+  }'
 ```
 
-#### Method 2: Call using Python
+### Method 2: Call using Python
 
 ```python
 import requests
 
 url = "https://cn-shanghai-alicloud-aimesh.api.singdata.com/gateway/v1/chat/completions"
 headers = {
-        "Authorization": "Bearer ${API_KEY}",
-        "Content-Type": "application/json",
+    "Authorization": "Bearer ${API_KEY}",
+    "Content-Type": "application/json",
 }
 payload = {
-        "model": "qwen/qwen3.6-plus",
-        "messages": [{"role": "user", "content": "hello"}],
+    "model": "qwen/qwen3.6-plus",
+    "messages": [{"role": "user", "content": "hello"}],
 }
 
 resp = requests.post(url, headers=headers, json=payload, timeout=60)
@@ -135,10 +140,18 @@ print(resp.status_code)
 print(resp.text)
 ```
 
-#### Example of a Successful Response
+### Example of a Successful Response
 
 If the call succeeds, you will see a response similar to the following:
 
 ```json
 {"text":"Hello! How can I help you today?","type":"text"}
 ```
+
+---
+
+## Related Documentation
+
+- [AI Gateway Overview](Introduction.md) — AI Gateway feature overview and architecture
+- [Model Pricing](pricing-ai-gateway.md) — Pricing and Token calculation rules for each model
+- [AI-Enhanced Data Analysis: Calling LLMs in SQL](lakehouse-ai-sql-analysis.md) — Call LLMs via AI Gateway in SQL

package/bin/skills/lakehouse-doc-en/references/quickstart_datashare_between_companies.md

@@ -53,12 +53,10 @@ WHERE     seller_id = '05e107217c7266362fd44b75b2cd4cc4';
 * Log into the Singdata Lakehouse console using an account with the "Instance Administrator" (`instance_admin`) role.
 * In the left navigation, select "Data" → "Data Sharing", and click "+ New Share".
 
-:-: ![](.topwrite/assets/image_1740388043727.png =742)
 
 * In the dialog, fill in the share name (e.g., shipping_detail), and select the workspace where the data to be shared is located.
 * Note: The data to be shared must be in the same workspace. If the data itself is distributed across multiple workspaces, you can create views of the data to be shared from other workspaces within one workspace to centralize all data to be shared into the same workspace.
 
-:-: ![](.topwrite/assets/image_1740388342928.png =438)
 
 **2) Add Data Objects to Share**
 
@@ -66,7 +64,6 @@ Continuing in the Create Share dialog, click "Add" and select the objects to sha
 
 After clicking "Done", the view will be included in the share list.
 
-:-: ![](.topwrite/assets/image_1740388392799.png =537)
 
 ^
 
@@ -74,7 +71,6 @@ After clicking "Done", the view will be included in the share list.
 
 In the same dialog, click the "Add" button below "Recipient Instances", enter Enterprise B's Singdata Lakehouse "Service Instance Name" (which Enterprise B needs to provide; it can be found in the upper right area of the homepage after logging into their service instance), and click Done.
 
-:-: ![](.topwrite/assets/image_1740388438814.png =531)
 
 ^
 
@@ -88,7 +84,6 @@ Subsequently, you can edit this Data Share to add or remove data objects to shar
 
 After creation, you can see the newly created Data Share object in the "Data Sharing" → "Shared by Me" list.
 
-:-: ![](.topwrite/assets/image_1740390203623.png =718)
 
 ^
 

package/bin/skills/lakehouse-doc-en/references/quickstart_envirment_for_team.md

@@ -38,17 +38,14 @@ To achieve the above management goals, you need to create independent users for
 
 Log in to the Singdata product using the default user created during account registration, go to the management center page, and switch to the "User Management" function:
 
-:-: ![](.topwrite/assets/quickstart_team_p1.png =801)
 
 ^
 
 Click the "New" button in the upper right corner and select "New User." Here, create two users: developer and analyst, as shown below:
 
-:-: ![](.topwrite/assets/quickstart_team_p2.png =361)
 
 ^
 
-:-: ![](.topwrite/assets/quickstart_team_p3.png =360)
 
 After successful creation, you can see these two users in the user list under user management.
 
@@ -58,23 +55,19 @@ In Lakehouse, a workspace is used to isolate computing resources and data, formi
 
 Log in using the user created during tenant registration, and click the name of the opened service instance in the management center to enter the service instance homepage.
 
-:-: ![](.topwrite/assets/quickstart_team_p4.png =797)
 
 ^
 
 On the service instance homepage, click "Management" - "Workspace" in the left menu to enter the workspace management page. Click the "+ New Space" button in the upper right corner:
 
-:-: ![](.topwrite/assets/quickstart_team_p5.png =774)
 
 ^
 
 Enter the workspace name in the pop-up window and click "OK" to complete the workspace creation:
 
-:-: ![](.topwrite/assets/quickstart_team_p6.png =382)
 
 ^
 
-:-: ![](.topwrite/assets/quickstart_team_p7.png =733)
 
 ^
 
@@ -84,11 +77,9 @@ In the Lakehouse workspace, schema is used to further categorize data tables and
 
 First, click "Develop" on the right side of the newly created dev\_envirment workspace to enter the development page, and execute the following SQL to create the schema:
 
-:-: ![](.topwrite/assets/quickstart_team_p8.png =730)
 
 ^
 
-:-: ![](.topwrite/assets/quickstart_team_p9.png =736)
 
 Create two tables in Schema STG and insert some sample data:
 
@@ -176,19 +167,16 @@ The above authorization operations, including adding users to the workspace and
 
 Continue using the user who created the dev\_environment workspace, click on "Management" - "Workspace" in the left menu to enter the workspace list, find the dev\_environment workspace, and click to enter. On the "Users" tab of the workspace details page, click the "+ Add User" button on the right:
 
-:-: ![](.topwrite/assets/quickstart_team_p10.png =774)
 
 ^
 
 In the pop-up window, find the user developer and check the box (you can also find the analyst user and check the box together. However, since the permissions to be granted to the two users are different, operate separately here, only add the developer user first).
 
-:-: ![](.topwrite/assets/quickstart_team_p11.png =763)
 
 ^
 
 At this point, there are two buttons below, click the right "Add User" button to only perform the operation of adding the user to the workspace without any authorization. Click the left "Add User and Grant Role" button to further select the role to be granted. Suppose we click the left "Add User and Grant Role" button:
 
-:-: ![](.topwrite/assets/quickstart_team_p12.png =772)
 
 ^
 
@@ -208,10 +196,6 @@ Execute the following statement in the development function:
 SHOW GRANTS TO USER developer;
 ```
 
-The results are as follows:
-
-:-: ![](.topwrite/assets/quickstart_team_p13.png =738)
-
 ^
 
 ### 3.7 Team Member Login to the System
@@ -220,23 +204,19 @@ After completing the above operations, both the developer and analyst users can
 
 Return to the Singdata login page <https://accounts.singdata.com/login>, and sequentially enter the account name, username, and password. The account name is provided after the account registration is successful and can be obtained from the URL after any user of the account logs in.
 
-:-: ![](.topwrite/assets/quickstart_team_p15.png =746)
 
 Now, use the developer user to log in at the .accounts.singdata.com/login URL, and click the "Enter" service instance button under the "Lakehouse" product to enter the Lakehouse service instance.
 
-:-: ![](.topwrite/assets/quickstart_team_p16.png =740)
 
 ### 3.8 Team Member Writing Development Tasks
 
 After the developer user logs in, go to the "Development" page in the left menu. Since the current developer user has only joined the dev\_environment workspace, there is no need to switch workspaces. If multiple workspaces are joined, you can switch to the required workspace for development in the upper right corner.
 
-:-: ![](.topwrite/assets/quickstart_team_p17.png =739)
 
 ^
 
 Click the "+" to create a new SQL script in the "Development" function, and write a query statement to query the data in the stg.employees table.
 
-:-: ![](.topwrite/assets/quickstart_team_p18.png =717)
 
 ^
 
@@ -244,25 +224,21 @@ Click the "+" to create a new SQL script in the "Development" function, and writ
 select * from stg.employees limit 10;
 ```
 
-:-: ![](.topwrite/assets/quickstart_team_p19.png =740)
 
 ^
 
 Click the "Save" button to save the task code, and the "Schedule" button to open the schedule configuration popup.
 
-:-: ![](.topwrite/assets/quickstart_team_p20.png =572)
 
 ^
 
 In the popup, configure the scheduling task's cycle, rerun method, and other information, then click the "OK" button to complete the scheduling configuration operation for the task.
 
-:-: ![](.topwrite/assets/quickstart_team_p21.png =730)
 
 ^
 
 After successfully configuring the schedule, the "Submit" button becomes clickable. After clicking "Submit," the task is submitted for periodic scheduling.
 
-:-: ![](.topwrite/assets/quickstart_team_p22.png =695)
 
 ^
 

package/bin/skills/lakehouse-doc-en/references/realtime-pipeline-selection-guide.md

@@ -252,8 +252,7 @@ CREATE PIPE ods.kafka_events_pipe AS
 
 -- Step 3: Create Dynamic Table for minute-level aggregation (DWD layer)
 CREATE DYNAMIC TABLE dwd.event_stats
-    TARGET_LAG = '1 minute'
-    VCLUSTER = 'default'
+    REFRESH INTERVAL 1 MINUTE VCLUSTER DEFAULT
 AS
 SELECT
     DATE_TRUNC('minute', ts)  AS minute,

package/bin/skills/lakehouse-doc-en/references/realtime-sales-dashboard-with-dynamic-table.md

@@ -126,7 +126,7 @@ Join the orders table with the products table to add category and brand informat
 
 ```sql
 CREATE OR REPLACE DYNAMIC TABLE doc_dwd_order_detail
-REFRESH INTERVAL '1' MINUTE VCLUSTER default
+REFRESH INTERVAL '1' MINUTE VCLUSTER DEFAULT
 AS
 SELECT
     o.order_id,
@@ -151,7 +151,7 @@ Aggregate by category to compute order count, total quantity, GMV, and average p
 
 ```sql
 CREATE OR REPLACE DYNAMIC TABLE doc_ads_category_gmv
-REFRESH INTERVAL '1' MINUTE VCLUSTER default
+REFRESH INTERVAL '1' MINUTE VCLUSTER DEFAULT
 AS
 SELECT
     category,
@@ -171,7 +171,7 @@ Compute real-time rankings based on the GMV summary table.
 
 ```sql
 CREATE OR REPLACE DYNAMIC TABLE doc_ads_category_rank
-REFRESH INTERVAL '1' MINUTE VCLUSTER default
+REFRESH INTERVAL '1' MINUTE VCLUSTER DEFAULT
 AS
 SELECT
     RANK() OVER (ORDER BY gmv DESC) AS gmv_rank,

package/bin/skills/lakehouse-doc-en/references/realtime_sync.md

@@ -26,5 +26,4 @@ Here, we take the real-time sync of Kafka data source to Lakehouse as an example
 
   After submission, you can perform start and stop operations and monitoring of real-time sync tasks in the Operations Center.
 
-
 ^

package/bin/skills/lakehouse-doc-en/references/release-note-2026-05-19.md

@@ -1,3 +1,5 @@
+# Release Notes 2026-05-19
+
 ^
 
 **Product Upgrade Notice**: Starting with this release, DataGPT is officially renamed to **Analytics Agent**. Product capabilities remain unchanged; only the product name has been upgraded. Subsequent documentation and UI will gradually switch to the new name.
@@ -19,15 +21,15 @@ This release introduces a series of new features, enhancements, and fixes. Pleas
 
 * [Row-Level Permissions](https://www.singdata.com/documents/row_level_permission) Enhancements:
   * When configuring row-level permissions, administrators can now dynamically obtain permission scopes from other data tables using expressions (e.g., automatically retrieving a user's assigned store list from a store table), in addition to manually entering fixed values. Suitable for scenarios where permission values change frequently or need to follow business data updates automatically.
-* **Dashboard Version Management**:
+* [Dashboard Version Management](https://www.singdata.com/documents/dashboard-version-management-guide):
   * Each modification to a dashboard chart via ASK AI conversation automatically generates a version. Users can view thumbnail previews and modification history of historical versions in the version panel, with support for one-click preview and restore. Solves the pain point of "can't undo after breaking things" — revert at any time if unsatisfied.
-* **Open API**:
+* [Open API](https://www.singdata.com/documents/open-api-overview):
   * Supports initiating data analysis requests and retrieving results via API, making it easy to embed Analytics Agent's analysis capabilities into internal enterprise systems, workflows, or custom applications for automated data Q&A.
 * **Automatic Chart Error Correction**:
   * When AI generates charts, the system automatically detects rendering errors and attempts to fix them, reducing cases of "chart display anomalies" — users can get correct visualization results without manual retries.
 * **Scheduled Task Email: Chinese/English Bilingual and Multiple Recipients**:
   * Scheduled analysis report emails now support Chinese/English language adaptation and can be sent to multiple recipients simultaneously.
-* **Chart Auto-Refresh Configuration**:
+* [Chart Auto-Refresh Configuration](https://www.singdata.com/documents/chart-auto-refresh-guide):
   * Dashboard charts now support setting an auto-refresh interval (default: 24 hours). The system automatically updates chart data at the configured time without manual refresh.
 
 ## Improvements

package/bin/skills/lakehouse-doc-en/references/revoke-privileges.md

@@ -1,3 +1,5 @@
+# REVOKE
+
 ## Function Description
 
 Revokes previously granted privileges from a role or user. The `REVOKE` statement can revoke permissions at various levels, including workspace, workspace object, Schema, and Schema object levels.
@@ -32,7 +34,7 @@ FROM { ROLE role_name | USER user_name };
 2. Revoke from role `simple_role` the `ALTER` privilege on the VCLUSTER named `default`:
 
    ```SQL
-   REVOKE ALTER VCLUSTER ON VCLUSTER default FROM ROLE simple_role;
+   REVOKE ALTER VCLUSTER ON VCLUSTER DEFAULT FROM ROLE simple_role;
    ```
 
 3. Revoke from role `uat_demo` the privilege to create tables and views in the `public` Schema:

package/bin/skills/lakehouse-doc-en/references/roles.md

@@ -56,16 +56,15 @@ Roles can be granted to users via the Web interface or SQL.
 
 On the **Security > Roles** page, you can view instance-level roles and workspace-level roles under the current instance.
 
-:-: ![](.topwrite/assets/image_1734878372389.png =784)
+
 
 To authorize any role, click the role name to enter the role details page, where you can see all users who have been granted this role. Click **+ Grant User**, select the users to add in the dialog, and click **Authorize** to grant the role to the users.
-:-: ![](.topwrite/assets/image_1734878510613.png =798)
+
 
 To remove a user who has been granted a role, click the "..." to the right of the username and select **Remove User** to revoke that user's permission to use this role.
 
 On the **Management > Workspaces** list, enter the workspace details page, and on the **Roles** tab you can also view the role list within that workspace and perform the above operations to grant or revoke roles to/from users.
 
-:-: ![](.topwrite/assets/image_1734878871234.png =795)
 
 **SQL Operation**