How many issues can be potentially stored on a Jira instance? Millions, of course.
So, do you realize how much reckless would be running this query?
select * from ISSUE
It does not make any sense allowing users to run such reckless queries. So the app introduces some column constraints to avoid them:
A Full scan error is raised by the engine, displaying the required columns to run: JQL and ID in this case.
Many built-in tables (AKA as dynamic tables) require some values to work. This might result a bit annoying for users not used to this behavior at the beginning.
Tip: to discover the column constraints of a particular table, simple explore the table values as it shown in example below.
show columns from ISSUE
Full scan of numerous built-in tables are not allowed. Full scan means that SQL engine requires to read all the data from the table to resolve the user’s query. This is not optimal and it may cause productivity and other reliability issues of Jira server or user’s browser. As mentioned, the engine introduces the concept of column constraints to force 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:
select * from ISSUE where JQL = ' project = SSP '
The results are displayed on a flat table.