[ https://issues.jboss.org/browse/TEIID-3646?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-3646: ------------------------------- Description: When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query. The tested query: {code:sql} /*+ cache */ SELECT * FROM Customers OPTION NOCACHE {code} Test scenario: Insert value into db, directly through its jdbc driver: {code:sql}INSERT INTO Customers VALUES(1, 'name1'){code} Check via teiid, that query returns one row. This result set should not be cached. {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code} Insert another row into db, via its jdbc driver, not through teiid: {code:sql}INSERT INTO Customers VALUES(2, 'name2'){code} Check that this query returns again current state of db (2 rows) now: {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code} But this check fails, teiid returns only one row, seemingly the result set for query with 'OPTION NOCACHE' gets cached. was: When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query. The tested query: {code:sql} /*+ cache */ SELECT * FROM Customers OPTION NOCACHE {code} Test scenario: Insert value into db, directly through its jdbc driver: {code:sql}INSERT INTO Customers VALUES(1, 'name1'){code} Check via teiid, that query returns one row. This result set should not be cached. {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code} Insert another row into db, via its jdbc driver, not through teiid: {code:sql}INSERT INTO Customers VALUES(2, 'name2'){code} Check that this query returns again current state of db (2 rows) now: {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code} But this check fails, teiid returns only one row, seemingly the result set for command with 'OPTION NOCACHE' gets cached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)