...
Full scans on many built-in tables are not allowed. Full scan means that the SQL engine requires to read all the data from the table to resolve the user’s query. This is not optimal and it could cause performance and other reliability issues on the Jira server or on the user’s browser. As mentioned, the engine introduces the concept of column constraints to force the user to set a limited scope for the table data and the query will be aborted with a full scan error raised by the engine if a full scan is detected on a constrained dynamic table.
How to run a query against a constrained table? Simple: provide values for the required constrained columns. This can be done via where clause or join conditions as shown in the example below:
| Code Block |
|---|
select * from ISSUE where JQL = ' project = SSP ' |
...
The results are displayed on a flat table.