...
Default
SQL that will be used when not using individual operations like get, insert, update, etc.
Example:
| Code Block |
|---|
SELECT id, year, make, model FROM auto_info WHERE year = {:2} AND make = {:3} AND model = {:4} |
Get
SQL used to determine how data will be retrieved from the database.
Example:
| Code Block | ||
|---|---|---|
| ||
SELECT id, year, make, model FROM auto_info WHERE year = {:2} AND make = {:3} AND model = {:4} |
Set
SQL code used to determine how data will be set in Jira, not the database.
Insert
SQL code used to determine how data will be inserted into the database.
Example:
| Code Block | ||
|---|---|---|
| ||
INSERT INTO auto_info(id, year, make, model) VALUES ({:1}, {:2}, {:3}, {:4}) |
Update
SQL code used to determine how data will be updated in the database.
Example:
| Code Block | ||
|---|---|---|
| ||
UPDATE auto_info SET year = {:2}, make = {:3}, model = {:4} WHERE id = {:1} |
Delete
SQL code used to determine how data will be deleted from the database.
Example:
| Code Block | ||
|---|---|---|
| ||
DELETE FROM auto_info WHERE id = {:1} |
Search
SQL code used to determine how data will be searched in the database.
Example:
| Code Block | ||
|---|---|---|
| ||
SELECT id, year, make, model FROM auto_info WHERE model ~ {:4} |
Seq
SQL code used to determine a sequence value for the ID when inserting new values into the database. If not specified, it will try to use the value provided in the inputs, and if that does not exist, it will rely on the database to have a mechanism for the ID.
Example:
...
| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The Scripts tab allows you to configure the field’s scripts that will be run for each of the operations that the field supports. The supported operations can vary depending on the field’s display type.
For read-only fields, only a subset of operations are supported: DEFAULT, GET and SEARCH. More details here Configuring scripts for read-only fields
The generic fields allow you to configure the full list of operations: DEFAULT, GET, SET, INSERT, UPDATE, DELETE, SEARCH, SEQ. For a more detailed presentation check out Configuring scripts for generic fields
By default, the scripts are expected to contain SQL syntax, notice the lozenge next to each of the operations. If needed, SIL scripts can be used instead. To switch between the script types, simply right-click on the operation and select the desired option:
You don’t need to align all operations to the same script type, a mix of the two (SQL and SIL) is perfectly fine.
The presence or absence of scripts for each operation is highlighted using a certain color for the operation label. Operations marked in green already have a script configured, while the operations marked in red are lacking scripts. It is not mandatory to fill in a script for each operation, it all depends on how you are planning to use the field.
For SIL scripts we offer the Check functionality that allows you to verify a script’s syntax but for SQL we don’t have it. Please make sure that the SQL scripts that you configure are syntactically correct in relationship with the DBMS that you are using.
When selecting a certain script, an extra Details panel opens:
For each script you are able to use extra parameters, which can be either screen or issue Jira fields (standard or custom fields). More details on how to use script parameters here How to Use Script Parameters
Contents
| Table of Contents |
|---|
See More
| Child pages (Children Display) | ||||
|---|---|---|---|---|
|