Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:EclipseLink/UserGuide/JPA/Basic JPA Development/Caching/Shared and Isolated
< Talk:EclipseLink/UserGuide/JPA | Basic JPA Development
Revision as of 12:43, 4 May 2011 by Unnamed Poltroon (Talk) (New page: -- Ben Gelernter 5/03/11 : ELUG ref : I removed this reference to ELUG. Return here to see if this information needs to be brought forward into this doc....)
-- Ben Gelernter 5/03/11
- ELUG ref
- I removed this reference to ELUG. Return here to see if this information needs to be brought forward into this doc.
- Under "Isolated Client Sessions," second bullet:
- achieve serializable transaction isolation (see Isolated Client Session Cache);
- Under "Isolated Client Sessions," second bullet:
- Paragraph between the two notes:
- Client sessions can access the data source using a connection pool or an exclusive connection. To use an exclusive connection, acquire the isolated client session using a ConnectionPolicy (see How to Acquire a Client Session that Uses Exclusive Connections). Using an exclusive connection provides improved user-based security for reads and writes. Named queries can also use an exclusive connection (see Configuring Named Query Advanced Options).
- Paragraph between the two notes:
- Right after second note, before "Isolated Client Sessions and Oracle Virtual Private Database (VPD)":
- For more information, see the following:
- * Isolated Client Session Limitations
- * How to Acquire an Isolated Client Session
- * Configuring Exclusive Isolated Client Sessions for Virtual Private Database
- Right after second note, before "Isolated Client Sessions and Oracle Virtual Private Database (VPD)":