Skip to main content
Jump to: navigation, search

Difference between revisions of "Configuring Historical Sessions (ELUG)"

m (New page: <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ Related Topics</div> This section describes the vario...)
 
m
Line 5: Line 5:
 
For information on configuring a historical session using an Oracle Database platform, see [[#How to Configure Historical Sessions Using an Oracle Platform|How to Configure Historical Sessions Using an Oracle Platform]].
 
For information on configuring a historical session using an Oracle Database platform, see [[#How to Configure Historical Sessions Using an Oracle Platform|How to Configure Historical Sessions Using an Oracle Platform]].
  
For information on configuring a historical session using any supported database platform and a EclipseLink <tt>HistoryPolicy</tt>, see [[#How to Configure Historical Sessions Using a EclipseLink HistoryPolic|How to Configure Historical Sessions Using a EclipseLink HistoryPolicyy]].
+
For information on configuring a historical session using any supported database platform and a EclipseLink <tt>HistoryPolicy</tt>, see [[#How to Configure Historical Sessions Using a EclipseLink HistoryPolicy|How to Configure Historical Sessions Using a EclipseLink HistoryPolicy]].
  
 
For more information about historical sessions, see [[Introduction%20to%20EclipseLink%20Sessions%20(ELUG)#Historical Sessions|Historical Sessions]].
 
For more information about historical sessions, see [[Introduction%20to%20EclipseLink%20Sessions%20(ELUG)#Historical Sessions|Historical Sessions]].
Line 12: Line 12:
  
 
==Introduction to Historical Session Configuration==
 
==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:
 
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|How to Configure Historical Sessions Using an Oracle Platform]])
 
* using an Oracle platform (see [[#How to Configure Historical Sessions Using an Oracle Platform|How to Configure Historical Sessions Using an Oracle Platform]])
 
* using EclipseLink <tt>HistoryPolicy</tt> (see [[#How to Configure Historical Sessions Using a EclipseLink HistoryPolicy|How to Configure Historical Sessions Using a EclipseLink HistoryPolicy]])
 
* using EclipseLink <tt>HistoryPolicy</tt> (see [[#How to Configure Historical Sessions Using a EclipseLink HistoryPolicy|How to Configure Historical Sessions Using a EclipseLink HistoryPolicy]])
Line 21: Line 19:
  
 
===How to Configure Historical Sessions Using an Oracle Platform===
 
===How to Configure Historical Sessions Using an Oracle Platform===
 
 
Oracle9''i'' Database Server (or later) automatically maintains historical versions of objects and extends SQL with an <tt>AS_OF</tt> clause used to query this historical data. Oracle refers to these as flashback queries.
 
Oracle9''i'' Database Server (or later) automatically maintains historical versions of objects and extends SQL with an <tt>AS_OF</tt> clause used to query this historical data. Oracle refers to these as flashback queries.
  
Line 29: Line 26:
  
 
For more information, see the following:
 
For more information, see the following:
 
 
* [[Acquiring%20and%20Using%20Sessions%20at%20Run%20Time%20(ELUG)#Acquiring a Historical Session|Acquiring a Historical Session]]
 
* [[Acquiring%20and%20Using%20Sessions%20at%20Run%20Time%20(ELUG)#Acquiring a Historical Session|Acquiring a Historical Session]]
 
* [[Introduction%20to%20EclipseLink%20Queries%20(ELUG)#Historical Queries|Historical Queries]].
 
* [[Introduction%20to%20EclipseLink%20Queries%20(ELUG)#Historical Queries|Historical Queries]].
  
===How to Configure Historical Sessions Using a EclipseLink HistoryPolicy===
 
  
 +
 +
===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 <tt>HistoryPolicy</tt>, you can query the historical versions of objects maintained by your database in accordance with your schema.
 
If you use a schema that you designed to maintain historical versions of objects and if that schema can be described by EclipseLink <tt>HistoryPolicy</tt>, you can query the historical versions of objects maintained by your database in accordance with your schema.
  
 
For more information, see the following:
 
For more information, see the following:
 
 
* [[Configuring%20a%20Descriptor%20(ELUG)#Configuring a History Policy|Configuring a History Policy]]
 
* [[Configuring%20a%20Descriptor%20(ELUG)#Configuring a History Policy|Configuring a History Policy]]
 
* [[Acquiring%20and%20Using%20Sessions%20at%20Run%20Time%20(ELUG)#Acquiring a Historical Session|Acquiring a Historical Session]]
 
* [[Acquiring%20and%20Using%20Sessions%20at%20Run%20Time%20(ELUG)#Acquiring a Historical Session|Acquiring a Historical Session]]
 
* [[Introduction%20to%20EclipseLink%20Queries%20(ELUG)#Historical Queries|Historical Queries]].
 
* [[Introduction%20to%20EclipseLink%20Queries%20(ELUG)#Historical Queries|Historical Queries]].
 +
 +
  
  

Revision as of 13:51, 17 December 2007

This section describes the various components that you must configure in order to be able to use historical sessions.

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:


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:




Copyright Statement

Back to the top