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.
Configuring Historical Sessions (ELUG)
For the latest EclipseLink documentation, please see http://www.eclipse.org/eclipselink/documentation/
Contents
For information on configuring a historical session using an Oracle Database platform, see How to Configure Historical Sessions Using an Oracle Platform.
For information on configuring a historical session using any supported database platform and a EclipseLink HistoryPolicy, see How to Configure Historical Sessions Using a EclipseLink HistoryPolicy.
For more information about historical sessions, see Historical Sessions.
Introduction to Historical Session Configuration
There are two following ways to configure EclipseLink to access the historical versions of objects maintained by your data source:
- using an Oracle platform (see How to Configure Historical Sessions Using an Oracle Platform)
- using EclipseLink HistoryPolicy (see How to Configure Historical Sessions Using a EclipseLink HistoryPolicy)
How to Configure Historical Sessions Using an Oracle Platform
Oracle9i Database Server (or later) automatically maintains historical versions of objects and extends SQL with an AS_OF clause used to query this historical data. Oracle refers to these as flashback queries.
If you configure your Session with an OraclePlatform (see Configuring a Relational Database Platform at the Session Level) for Oracle9i Database Server (or later), you can query the historical versions of objects automatically maintained by Oracle Database.
No further session configuration is required.
For more information, see the following:
How to Configure Historical Sessions Using a EclipseLink HistoryPolicy
If you use a schema that you designed to maintain historical versions of objects and if that schema can be described by EclipseLink HistoryPolicy, you can query the historical versions of objects maintained by your database in accordance with your schema.
For more information, see the following: