keisuke-miyako/springsea-0.2
5B • Updated • 96
text stringlengths 269 63k |
|---|
As of 4D version 21, the `4D` command is used to retrieve the class store that contains all available built-in 4D classes. This command is designed to return an object representing the class store, which includes the definitions and properties of 4D's native classes.
The syntax for the `4D` command is as follows:
- ... |
As of 4D version 21, the **ABORT PROCESS BY ID** command is used to forcibly terminate a specific process running on 4D Server. The command adheres to the following syntax: `ABORT PROCESS BY ID (uniqueID)`.
This command accepts a single mandatory parameter:
- **uniqueID**: An integer value representing the unique ide... |
As of 4D version 21, the ABORT command is a specialized instruction designed for use exclusively within an error-handling project method that has been installed via the ON ERR CALL command. This command adheres to a straightforward syntax: ABORT, and it does not accept any parameters or modifiers.
In the absence of an... |
As of 4D version 21, the ACCEPT command is a built-in function that simulates the action of a user pressing the Enter key within a form or interactive dialog. This command does not accept any parameters and is invoked using the following syntax: `ACCEPT`. Upon execution, ACCEPT finalizes the current form interaction, a... |
As of 4D version 21, the ACCUMULATE command is used to specify which numeric fields or variables should be accumulated during the execution of a form report generated by the PRINT SELECTION command. This command is essential for implementing break processing in reports, where subtotals are calculated for grouped data. ... |
As of 4D version 21, the ACTIVITY SNAPSHOT command provides detailed monitoring of active operations within the 4D database environment. This command is designed to capture and return information about the most resource-intensive or frequently executed operations, such as cache writes or formula executions. The data re... |
As of 4D version 21, the `ADD RECORD` command is a long-standing feature of the 4D relational database management system, originally implemented in early releases and remaining relevant for prototyping and basic development workflows. The command facilitates the addition of new records to a specified table or the defau... |
As of 4D version 21, the ADD TO SET command is used to include the current record of a specified table into an existing set. This command ensures that the record is appended to the set without altering the set's prior contents. The syntax for the command is as follows: `ADD TO SET ({aTable;} set)`.
The command accept... |
As of 4D version 21, the ADJUST BLOBS CACHE PRIORITY command is designed for specialized use cases where fine-tuned control over the caching behavior of BLOB-related data is required. This command allows developers to dynamically adjust the cache priority of BLOB, text, picture, and object fields within a specified tab... |
As of 4D version 21, the ADJUST INDEX CACHE PRIORITY command is provided for specialized optimization scenarios within the 4D database environment. This command allows developers to dynamically modify the cache priority of index entries associated with a specified field for the duration of the current process. The comm... |
As of 4D version 21, the ADJUST TABLE CACHE PRIORITY command is provided for specialized cache management scenarios within the 4D environment. This command allows developers to dynamically modify the cache priority of scalar data associated with a specified table for the current process. The syntax for this command is ... |
As of 4D version 21, the ALERT command is used to present a modal alert dialog box to the user. This dialog box includes a note icon, a customizable message, and a single button labeled "OK" by default. The command syntax is structured as follows: ALERT(message{; okButtonTitle}).
The command accepts two parameters:
... |
As of 4D version 21, the ALL RECORDS command is used to select all records belonging to a specified table within the context of the current process. This command ensures that every record in the designated table is included in the current selection for subsequent operations. The syntax for the ALL RECORDS command is as... |
As of 4D version 21, the APPEND DATA TO PASTEBOARD command enables developers to append binary data to the system pasteboard (commonly referred to as the Clipboard in copy/paste operations) under a specified data type. This command is particularly useful for handling structured or non-textual data that needs to be tran... |
As of 4D version 21, the **APPEND MENU ITEM** command is used to append new menu items to an existing menu, identified either by its menu number or its menu reference (MenuRef). The command follows this syntax: `APPEND MENU ITEM (menu; itemText {; subMenu {; process {; *}}})`. Below is a detailed breakdown of its param... |
As of 4D version 21, the APPEND TO ARRAY command is used to extend an existing array by adding a new element at its end and assigning a specified value to that element. The command adheres to the following syntax: APPEND TO ARRAY(array; value).
The command requires two parameters:
- The first parameter, *array*, is ... |
As of 4D version 21, the **APPEND TO LIST** command is used to append a new item to an existing hierarchical list within the 4D environment. This command is particularly useful for dynamically constructing or modifying hierarchical lists, which are commonly employed in user interfaces to present structured data such as... |
As of 4D version 21, the `APPLY TO SELECTION` command is used to execute a specified *statement* on each record within the current selection of a given table. This command is particularly useful for batch operations, such as updating field values or gathering aggregated data from a set of records. The syntax for this c... |
As of 4D version 21, the ARRAY BLOB command is used to create and/or resize an in-memory array composed of elements of the Blob data type. This command allows developers to define either a one-dimensional or two-dimensional array structure, depending on the parameters provided. The syntax for the ARRAY BLOB command is ... |
As of 4D version 21, the ARRAY BOOLEAN command is used to create and/or resize an array of Boolean elements in memory. This command allows developers to define either a one-dimensional or two-dimensional Boolean array, depending on the parameters provided. The syntax for the ARRAY BOOLEAN command is as follows: `ARRAY ... |
As of 4D version 21, the ARRAY DATE command is used to create and/or resize an in-memory array specifically designed to store Date-type elements. This command supports both one-dimensional and two-dimensional arrays, depending on the parameters provided. The syntax for the ARRAY DATE command is as follows: ARRAY DATE(a... |
As of 4D version 21, the ARRAY INTEGER command is used to create and/or resize an array of 2-byte integer elements in memory. This command supports both one-dimensional and two-dimensional arrays, depending on the parameters provided. The syntax for the ARRAY INTEGER command is as follows: `ARRAY INTEGER(arrayName; siz... |
As of 4D version 21, the ARRAY LONGINT command is used to create and/or resize an array specifically designed to hold 4-byte signed integer values (commonly referred to as Longint or 4-byte Integer elements) in memory. This command allows developers to dynamically allocate and manage arrays of fixed-size integers withi... |
As of 4D version 21, the ARRAY OBJECT command is used to create and/or resize an in-memory array composed of elements of the language Object type. The command adheres to the following syntax: ARRAY OBJECT(arrayName; size{; size2}).
The command accepts up to three parameters:
- The first parameter, arrayName, is a re... |
The ARRAY PICTURE command is used to create and/or resize an in-memory array specifically designed to store Picture-type elements. The command adheres to the following syntax: ARRAY PICTURE(arrayName; size{; size2}).
The command accepts three parameters, two of which are mandatory and one optional. The first paramete... |
As of 4D version 21, the **ARRAY POINTER** command is used to create or resize an array whose elements are of the Pointer type, or which reference tables or fields in a 4D database. The command allocates memory for the array and initializes its elements according to the specified dimensions. The syntax for this command... |
As of 4D version 21, the ARRAY REAL command is used to create and/or resize an array of Real-type (floating-point) elements in memory. This command allows developers to define either a one-dimensional or two-dimensional array, depending on the parameters provided. The syntax for the ARRAY REAL command is as follows: `A... |
As of 4D version 21, the ARRAY TEXT command is used to create and/or resize an in-memory array composed of Text-type elements. This command supports the construction of both one-dimensional and two-dimensional arrays, depending on the parameters provided. The formal syntax for the command is as follows: ARRAY TEXT(arra... |
As of 4D version 21, the **ARRAY TIME** command is used to create and/or resize an in-memory array specifically designed to hold elements of the Time data type. This command provides flexibility in defining either one-dimensional or two-dimensional arrays, depending on the parameters supplied.
### Command Syntax
The *... |
As of 4D version 21, the **ARRAY TO COLLECTION** command facilitates the transfer of data from one or more 4D arrays into a collection, either as direct elements or as values assigned to specified properties within objects contained in the collection. The command adheres to the following syntax: `ARRAY TO COLLECTION ( ... |
As of 4D version 21, the ARRAY TO LIST command is used to create or replace a hierarchical list or a choice list (defined in the List editor) by populating it with elements from a specified array. The command follows this syntax: ARRAY TO LIST(array; list{; itemRefs}). Below is a detailed breakdown of its parameters, b... |
As of 4D version 21, the **ARRAY TO SELECTION** command enables the transfer of data from one or more arrays into a selection of records within a table. This command is particularly useful for bulk data operations, where array elements are mapped directly to fields in existing or newly created records. The formal synta... |
As of 4D version 21, the ASSERT command is used to evaluate a boolean expression (referred to as an assertion) during code execution. If the evaluated expression returns false, the command halts further execution of the code and raises an error. The syntax for the ASSERT command is as follows: ASSERT(boolExpression {; ... |
As of 4D version 21, the `Abs` command is used to compute the absolute value of a given numeric input. The absolute value of a number is its unsigned, positive equivalent, regardless of whether the original number is positive or negative.
The command follows this syntax: `Abs(number): Real`.
Detailed parameter and ... |
As of 4D version 21, the **Action info** command provides detailed status and availability information about a specified standard action within a given application context. This command is particularly useful for determining whether an action can be executed, its current state, and other relevant properties. The syntax... |
As of 4D version 21, the **Activated** command is an obsolete function that operates within the context of form methods. This command returns a Boolean value of **True** when the window containing the executing form becomes the frontmost window of the foremost process in the application. The syntax for this command is ... |
As of 4D version 21, the **Active transaction** command is used to determine whether the current process is actively engaged in a transaction that has not been suspended. This command returns a Boolean value, specifically **True** if the process is currently within an active, non-suspended transaction, and **False** if... |
As of 4D version 21, the **Add to date** command is a built-in function designed to modify a given date by adding specified quantities of years, months, and days, then returning the resulting date. The command adheres to the following formal syntax: `Add to date (date; years; months; days): Date`.
The command accepts... |
As of 4D version 21, the **After** command is a built-in function that evaluates the current execution cycle of a form event and returns a Boolean value indicating whether the cycle is an "after" phase. The command is designed to be used within form event handling logic to determine if the code is executing in response... |
As of 4D version 21, the **Append document** command provides functionality analogous to the **Open document** command, with a critical distinction in file positioning. This command is designed to open a document stored on disk, specifically positioning the file pointer at the end of the document, thereby facilitating ... |
As of 4D version 21, the `Application file` command retrieves the full (long) pathname of the currently executing 4D application or executable file. The command is invoked without any parameters and returns a single text value. The syntax is formally defined as follows: `Application file : Text`.
The returned text re... |
As of 4D version 21, the **Application info** command retrieves a comprehensive object containing detailed metrics and configuration settings related to the currently active 4D application. This command is designed to operate seamlessly in both standalone and client/server architectures, returning environment-specific ... |
As of 4D version 21, the **Application type** command is used to determine the specific type of 4D environment in which the application is currently executing. This command returns an integer value that corresponds to one of several predefined constants, each representing a distinct 4D environment or deployment mode. T... |
As of 4D version 21, the `Application version` command retrieves the version number of the currently running 4D environment in the form of an encoded string. The command supports an optional parameter to control the format and detail level of the returned version information. Its syntax is defined as follows: `Applicat... |
As of 4D version 21, the `Arctan` command calculates the arctangent of a given real number, returning the angle in radians whose tangent matches the input value. The command adheres to the following syntax: `Arctan(number): Real`.
The `Arctan` command accepts a single mandatory parameter:
- `number` (Real, input): Th... |
As of 4D version 21, the **Asserted** command functions analogously to the **ASSERT** command but distinguishes itself by returning the evaluated result of the provided Boolean expression. The command adheres to the following syntax: `Asserted(boolExpression {; messageText}) : Boolean`.
The command accepts two parame... |
As of 4D version 21, the `Average` command calculates the arithmetic mean (average) of a numeric series, which can be provided as a field, an array, or an object attribute. The command syntax is as follows: `Average(series {; attributePath}): Real`.
The `series` parameter, which is mandatory, specifies the data for w... |
As of 4D version 21, the BACKUP INFO command retrieves detailed information about the most recent backup operation performed on the database data. This command is designed to provide specific backup-related metadata based on the selector parameter provided. The syntax for the BACKUP INFO command is as follows: BACKUP I... |
As of 4D version 21, the BACKUP command initiates a backup procedure for the database, adhering to the backup configurations currently defined within the system. This command is invoked using the following syntax: `BACKUP`. It is important to note that the BACKUP command does not accept any parameters during its invoca... |
As of 4D version 21, the BASE64 DECODE command is used to decode a text or blob value that has been encoded in either Base64 or Base64URL format. The command syntax is as follows: BASE64 DECODE(toDecode {; decoded}{; *}).
The command accepts up to three parameters:
1. The *toDecode* parameter, which is mandatory and... |
As of 4D version 21, the **BASE64 ENCODE** command is used to encode a given text or blob value into either Base64 or Base64URL format. The command syntax is structured as follows: `BASE64 ENCODE (toEncode {; encoded}{; *})`.
The `toEncode` parameter, which is mandatory and the first in the sequence, accepts either a... |
As of 4D version 21, the BEEP command is a built-in function that triggers an audible beep sound on the host machine—either a PC or Macintosh—where the 4D application is executing. The command is designed to provide auditory feedback, typically used to alert the user to an event, condition, or error within the applicat... |
As of 4D version 21, the **BLOB PROPERTIES** command retrieves detailed metadata about a specified Binary Large Object (BLOB). This command is designed to provide insights into the compression status and size characteristics of a BLOB, enabling developers to optimize storage and processing operations effectively.
The ... |
As of 4D version 21, the BLOB TO DOCUMENT command is used to overwrite the entire contents of an existing document with the data stored in a Binary Large Object (BLOB). This command requires two parameters and follows the syntax: `BLOB TO DOCUMENT(document; blob)`.
The first parameter, `document`, is a text string th... |
As of 4D version 21, the **BLOB TO PICTURE** command enables the insertion of a picture stored in a Binary Large Object (BLOB) into a 4D picture variable or field, irrespective of the picture's original format. The command adheres to the following syntax: `BLOB TO PICTURE(pictureBlob; picture{; codec})`.
The command ... |
As of 4D version 21, the BLOB TO USERS command is used to replace the user accounts and groups stored in the current database with those contained in a specified BLOB. The command syntax is defined as follows: BLOB TO USERS (users).
The command accepts a single parameter:
- users: This parameter is a BLOB that must c... |
As of 4D version 21, the **BLOB TO VARIABLE** command is used to reconstruct a 4D variable from its serialized form stored within a BLOB (Binary Large Object). This command allows developers to extract data from a BLOB and write it directly into a specified variable, optionally starting from a designated byte offset wi... |
As of 4D version 21, the `BLOB size` command is used to determine the size, in bytes, of a specified Binary Large Object (BLOB). This command is particularly useful when managing BLOB-type fields or variables, as it provides a straightforward method to retrieve their storage size.
The syntax for the `BLOB size` comma... |
As of 4D version 21, the `BLOB TO INTEGER` command extracts a 2-byte signed integer value from a specified Binary Large Object (BLOB). The command adheres to the following syntax: `BLOB TO INTEGER(blob; byteOrder {; offset}): Integer`.
The command accepts three parameters:
1. **blob** (Type: BLOB, Direction: Input) ... |
As of 4D version 21, the **BLOB TO LIST** command enables developers to reconstruct a hierarchical list from binary data stored in a BLOB (Binary Large Object). The command reads the BLOB starting at a specified byte offset and generates a new list in memory, returning a reference number that identifies this list for s... |
As of 4D version 21, the **BLOB to longint** command extracts and returns a 4-byte signed long integer value from a specified binary large object (BLOB). The command adheres to the following syntax: `BLOB to longint(blob; byteOrder {; offset}): Integer`.
The command accepts three parameters, one of which is optional.... |
As of 4D version 21, the **BLOB to print settings** command is used to replace the current 4D print settings with parameters stored in a Binary Large Object (BLOB). This command is particularly useful for restoring predefined print configurations dynamically within an application. The command syntax is as follows: `BLO... |
As of 4D version 21, the `BLOB to real` command is used to extract a real (floating-point) numerical value from a specified Binary Large Object (BLOB). The command interprets a sequence of bytes within the BLOB as a real number and returns it in the 4D Real data type. The full syntax of the command is as follows: `BLOB... |
As of 4D version 21, the BLOB to text command converts binary data stored in a BLOB (Binary Large Object) into a human-readable text string. This command is particularly useful when extracting textual information from binary data, such as files or database fields, while specifying the encoding and format of the text co... |
As of 4D version 21, the BOOLEAN ARRAY FROM SET command is used to populate a Boolean array that indicates whether each record in a specified table is included in a given set. This command requires precise syntax and parameter handling to function correctly.
The command syntax is defined as follows: BOOLEAN ARRAY FRO... |
As of 4D version 21, the BREAK LEVEL command is used to define the number of break levels in a report generated by the PRINT SELECTION command. This command is essential for enabling and configuring break processing within reports, allowing for structured data grouping and subtotal calculations. The syntax for the BREA... |
As of 4D version 21, the BRING TO FRONT command is used to reposition all windows associated with a specified process to the frontmost level of the application's window hierarchy. This command is particularly useful for ensuring that a process's entire window set becomes visible and accessible to the user, overriding a... |
As of 4D version 21, the BUILD APPLICATION command initiates the process of generating a standalone or merged application from a 4D project. This command is designed to compile and package the application based on predefined settings, ensuring that all components are correctly integrated into the final build. The comma... |
As of 4D version 21, the `Before selection` command is used to determine whether the current record pointer is positioned before the first record in the current selection of a specified table. This command returns a Boolean value: `TRUE` if the pointer is before the first record, and `FALSE` otherwise.
The syntax for... |
As of 4D version 21, the **Before** command is a built-in function that evaluates the current execution cycle of a form event and returns a Boolean value indicating whether the cycle is the "Before" phase. The command is structured as follows:
The **Before** command adheres to the syntax:
**Before** : Boolean
When in... |
As of 4D version 21, the `Begin SQL` command is a keyword utilized within the Method editor to signal the start of a sequence of SQL commands. These commands are subsequently interpreted by the current data source associated with the process. The data source may either be the integrated SQL engine of 4D or an external ... |
As of 4D version 21, the **Bool** command is used to convert a given expression into its boolean equivalent. This command adheres to the following syntax: `Bool(expression): Boolean`.
The **Bool** command accepts a single parameter:
- `expression` (mandatory): This parameter represents any valid 4D expression whose b... |
As of 4D version 21, the **CALL FORM** command enables the execution of 4D code specified in a *formula* within the context of a form displayed in a designated *window*, irrespective of the process that owns the window. This command facilitates interprocess communication by allowing a calling process—whether cooperativ... |
End of preview. Expand in Data Studio
Commands
Clean summary of 4D language reference.
Abstract
LLMs are generally incapable of understanding 4D code. LoRA by exposure to raw source code would actually increase the rate of hallucination as the model gets confused between 4D code and C#, Visual Basic, or JavaScript.
CPT, or continued pre-training, based on grammar and vocabulary should moderate the model's attention before extensive fine-tuning using raw source code.
This dataset was generated with Mistral Large 3.
The following resources were used to produce the raw input:
- The public documentation from https://github.com/4d/docs
- The syntaxEN.json file
- The
Command namecommand
Special attention was place on the following rules:
- Specify the version
- Remove markdown tables
- Decompose and explain the syntax in neurtal format
Goal
The objective is to fine-tune the model to recognise dustinct patterns in 4D code. A benchmark would be a task such as "rewrite this version X code using version Y command set".
Example
As of 4D version 21, the Cache info command provides detailed insights into the current state of the database cache, including memory usage, loaded tables, indexes, and other cached elements. This command is designed to return an object containing comprehensive cache-related data, which can be invaluable for performance monitoring and optimization.\n\n### Syntax\nThe Cache info command follows this syntax:\n\nCache info {( dbFilter )} : Object\n\n\n### Parameters\n- dbFilter (Object, optional, input →): This parameter allows you to define the scope of the cache information returned by the command. It filters the results based on the specified database(s). The dbFilter object supports the following configurations:\n - If the dbFilter attribute is set to \"All\", the command returns cache information for all running databases, including any loaded components.\n - If the dbFilter attribute is set to an empty string (\"\"), the command returns cache information exclusively for the current database. This behavior is equivalent to omitting the dbFilter parameter entirely.\n\n### Return Value\n- Function Result (Object, output ←): The command returns a single object that encapsulates all relevant cache information. The structure of this object includes an array of root elements (such as tables, indexes, and BLOBs) currently loaded in the cache. Each element in this array contains specific attributes that describe its status, such as memory allocation, usage statistics, and other metadata. For advanced interpretation of this data, users are advised to consult their local 4D Technical Service department.\n\n### Operational Notes\n- The Cache info command is restricted to local mode operation. It functions correctly when executed in 4D (single-user) or 4D Server environments but must not be used in 4D remote mode (client-side execution).\n- By default, if the dbFilter parameter is omitted, the command returns cache information for the currently running database only.\n\n### Examples\n1. **Retrieving Cache Information for the Current Database:**\n To obtain cache details for the active database, you can call the command without any parameters:\n \n $cacheInfo := Cache info\n \n This will return an object containing cache data specific to the current database.\n\n2. **Retrieving Cache Information for All Databases:**\n To extend the scope to include all running databases and components, use the dbFilter parameter with the \"All\" value:\n \n $cacheInfo := Cache info(New object(\"dbFilter\"; \"All\"))\n \n This will return a consolidated object containing cache information for the current database and any opened components.\n\n### Additional Properties\n- Command Number: The internal identifier for the Cache info command is 1402.\n- Thread Safety: The Cache info command is thread-safe, meaning it can be safely executed in a multi-threaded environment without risking data corruption or inconsistent results.\n\n### Version History\n- The Cache info command was introduced in 4D v16.
- Downloads last month
- 1,494