Chronicle Element for EventClass/Chronicles (ADF)
Provides a location for specifying information about one event chronicle table.
Syntax
<EventClasses>
<EventClass>
...
<Chronicles>
<Chronicle>
Element Characteristics
| Characteristic | Description |
|---|---|
Data type |
None. |
Default value |
None. |
Occurrence |
Required once or more within a Chronicles element. |
Updates |
Can be added and deleted when updating the application. |
Element Relationships
| Relationship | Elements |
|---|---|
Parent element |
|
Child elements |
ChronicleName Element for EventClass/Chronicles/Chronicle (ADF) |
Remarks
Event chronicles are optional; use the Chronicle element and its child elements only if you need to maintain event information outside of the event tables used by an event class. A common reason to use event chronicles is to store and maintain event data for scheduled subscriptions. For more information, see Defining Chronicles for an Event Class.
Important
If you delete a Chronicle element, updating the application deletes and re-creates the event class to which the chronicle corresponds. This includes dropping and re-creating the Microsoft SQL Server tables and indexes used by the event class.
Example
The following example shows a Chronicle node that deletes any existing table named StockEventChon and then creates the StockEventChron event chronicle table.
<Chronicle>
<ChronicleName>StockEventChron</ChronicleName>
<SqlSchema>
<SqlStatement>
IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_NAME = 'StockEventChron')
DROP TABLE StockEventChron
</SqlStatement>
<SqlStatement>
CREATE TABLE StockEventChron
(
StockSymbol char(10),
StockHighPrice money
PRIMARY KEY (StockSymbol)
)
</SqlStatement>
</SqlSchema>
</Chronicle>
See Also
Reference
Application Definition File Reference
Other Resources
Defining Event Chronicle Tables
Defining Chronicles for an Event Class
Updating Instances and Applications