Bug 1260896 - Caching Guide - User Query Cache
Caching Guide - User Query Cache
Status: CLOSED CURRENTRELEASE
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Documentation (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity unspecified
: CR2
: 6.2.0
Assigned To: David Le Sage
Jan Stastny
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-08 03:32 EDT by Jan Stastny
Modified: 2015-09-28 20:56 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Build Name: 23073, Development Guide Volume 5: Caching Guide-6.2 Build Date: 04-09-2015 14:10:18 Topic ID: 43090-769664 [Latest]
Last Closed: 2015-09-28 20:56:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Stastny 2015-09-08 03:32:21 EDT
Title: User Query Cache

Describe the issue:
Duplicate note (it is repeated later in a NOTE):
> Note that if either of these mechanisms are used, Teiid must also have result set caching enabled (the default is enabled). 

Also whole this fragment is duplicate:
> End users or client applications explicitly state whether to use result set 
> caching. This can be done by setting the JDBC ResultSetCacheMode execution 
> property to true (by default it is set to false):
>
>  
>
> Properties info = new Properties();
>
> ...
> 
> info.setProperty("ResultSetCacheMode", "true");
> 
> Connection conn = DriverManager.getConnection(url, info);
>  
>
> Another way to do this is by adding a Cache Hint to the query. Note that if 
> either of these mechanisms are used, Teiid must also have result set caching 
> enabled (the default is enabled). 

Suggestions for improvement:


Additional information:
Comment 1 David Le Sage 2015-09-08 20:13:34 EDT
Thanks. Duplicated paragraphs removed.

Note You need to log in before you can comment on or make changes to this bug.