PROJECTS |
|
|
|
|
|
|
|
|
Column |
ID |
KEY |
NAME |
DESCRIPTION |
CATEGORY |
LEAD |
URL |
COUNTER |
Type |
BIGINT |
VARCHAR |
VARCHAR |
VARCHAR |
VARCHAR |
VARCHAR |
VARCHAR |
BIGINT |
Indexed |
|
|
|
|
|
|
|
|
A common mistake is try to get the project issues via the PROJECTS table joined with the ISSUE table
select * from projects p inner join issues i on p.id=i.projectid
The query above is correct from the semantic point of view and most JIRA users would expect it shows all the issues on JIRA. Therefore, all the relational database systems (Oracle, MySQL, H2, PostgreSQL, SQLServer, etc) would execute it.
However, SQL for JIRA is different. The SQL query above might compromise the JIRA Server performance (CPU and memory resources).Therefore, it is aborted by the SQL for JIRA plugin by raising a FULL SCAN exception. Please, read the ISSUES table documentation in order to understand way.