]
RH Bugzilla Integration commented on TEIID-3646:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug
Teiid Result Set Caching OPTION NOCACHE problem
-----------------------------------------------
Key: TEIID-3646
URL:
https://issues.jboss.org/browse/TEIID-3646
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.1.6_2
Reporter: Jan Stastny
Assignee: Steven Hawkins
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.