Enhancements included:
Supported suggestion and auto-completion for table names, field names, and other information.
Allowed debugging selected code blocks.
Supported multiple SELECT query statements in a single script.
Supported syntax checking and error highlighting.
Supported SQL statement formatting beautification.
Introduced an edit lock: When the content in the SQL editor was being edited, others could only preview it.
Decoupled the right-side SQL editor from the left-side data connection panel.
Managed SQL scripts independently.
Organized SQL scripts within the directories of their data connections.
Displayed the total row count in query results and supported data export.
During data development, you can write and debug SQL statements in FineDataLink and preview execution results without switching to external tools.
For FineDataLink of V4.1.9.2 and later versions, you must have registered the Database Table Management function point. For details, see Function Point Limit.
You must have permission to use the Database Table Management function. For details, see Data Platform Use Permission.
In Database Table Management, all SQL scripts associated with the same data connection are displayed in the Debugging Script directory of that data connection. You can view all SQL scripts for data sources within your permission scope.
The number of SQL scripts is displayed on the right side of the Debugging Script directory, as shown in the following figure.
You can click the icon to create an SQL script for the data connection, as shown in the following figure.
The data connection name is displayed in the SQL script toolbar, as shown in the following figure.
You can open and manage multiple scripts associated with different data connections in the right area. Each script is fully independent. You can click a tab to switch between scripts. Switching the left-side data connection does not affect the right-side editing area, as shown in the following figure.
You can write SQL statements for the selected data connection and debug them, as shown in the following figure.
Save the file after editing it. The SQL script is saved in the Debugging Script directory of the corresponding data connection, as shown in the following figure.
The following operations are available in the SQL editor:
You can tick Enhanced Completion to get suggestions for table names, field names, and more. Note that enabling this function may affect performance, as shown in the following figure.
Suggestion and auto-completion apply to:
Database/schema names, table/view names, and field names
Core keywords and built-in functions (excluding metadata management statements)
Syntax errors are highlighted in red. You can hover over the error to view the error type, as shown in the following figure.
The check scope includes:
Check whether table/view/field names exist in the connected data source.
Check whether core keywords (such as SELECT) and built-in functions are spelled correctly.
Check whether parentheses (()) are properly paired.
Check whether operators (==, !=, <>, >, <) are used correctly.
Check whether quotation marks are used correctly.
You can execute partial statements in a script.
Select the statements and click Execute at the top, or right-click the statement and click Execute Selected Statement.
Long statements can be folded to hide non-critical code blocks, improving writing and maintenance efficiency.
The current editing line and matching bracket pairs are highlighted with background colors.
Right-click a tab to access the following options: Close, Close Others, Close All, and Rename.
If too many tabs cause visual clutter during tab switchover, you can quickly close tabs in batches or rename SQL files.
The toolbar provides options for saving and executing scripts and viewing execution records. The following table describes the details.
You can execute the statement. Execution records are displayed at the bottom, including the statements executed, logs, and results.
SQL: It displays the currently executed SQL statement only.
Log: It records the start time, end time, and status (success/failure) of the current execution.
Result: This tab is displayed only when execution succeeds.
From V4.2.14.1, a single script supports multiple SELECT query statements, in which case, multiple Result tabs are displayed.
Parameters are not supported in SQL statements.
You can click the icon to apply one-click formatting with automatic indentation and layout optimization, making the statement structure clearer and more readable.
You can enable Enhanced Completion to get suggestions for table names and field names. Note that enabling this function may affect performance.
For details, see the "Editing SQL Files" section of this document.
From V4.2.16.4, you can export the query results after executing an SQL query, as shown in the following figure.
You can export the results as an Excel or CSV file. For configuration details, see Function Description of the File Output Operator.
Click the icon of a debugging script, and you can rename or delete the script, as shown in the following figure.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy