Cached connections

Since the 7.8.0 all the connections are cached by default. The cache ensures that each Jira API Java method is called once with the same parameters. Cache is not persistent across connections: therefore each connection caches ad manages its own data individually. 

The cache is managed automatically (cache and clean up). However,  even it is very uncommonly required, the users can flush and disable the cache for each connection in particular.

Run

SELECT CACHE_FLUSH()

to flush the cached data for the current connection.

SELECT CACHE_ENABLE(FALSE)

to disable it.

Example: See how the cache is disabled in the query below with three simple steps:

SELECT *
FROM 
  ISSUES i
JOIN 
  ISSUETYPES it on it.ID = i.TYPEID
WHERE i.ID = 10000

...and with the cache disabled it would be:

SELECT *
FROM 
  (SELECT CACHE_ENABLE(FALSE) FROM DUAL) -- (1) Cache disabled
[LEFT] JOIN -- (2) Left Join might be required to force the irght execution order -> Disabling cache first
  ISSUES i ON  i.ID = 10000 -- (3) Moving the conditions from the WHERE caluse as a JOIN constraint may resolve issues
JOIN 
  ISSUETYPES it on it.ID = i.TYPEID