Index
Note: Page numbers followed by f indicate figures.
A
Accessibility, temporal data
11,
21Allen relationship queries
313–342point in time to period of time
333–341point in time to point in time
341–342Alternative temporal model
41–43Approval transaction
280–284deferred assertion group, applied to
283f,
284Asserted version rows
96,
142example of notation describing
131Asserted version tables, basic diagram of
126f,
130Asserted Versioning
,
24,
27,
47,
97,
161–162,
261–262,
390Allen relationship taxonomy
66fbusiness key, use of term
174in Information technology best practices
48,
75–94managed objects of
95,
197partitioning strategy for
374practical orientation of
53–54production queries and
115temporal data, approach to
43temporal data management and
52–53Asserted Versioning, implementation of
352Asserted Versioning databases
167,
173,
186production queries against
387Asserted Versioning Framework (AVF)
45,
53,
61,
113,
169–170,
191,
213,
222,
387Allen relationship used by
312deferred transactions workflow management and
394episode begin date, determining
220Asserted Versioning schema
bi-temporal, redundancies in
186–189Assertion begin date (Asr-beg)
64,
103–104,
121,
143Asserted Versioning model
128standard temporal model
128Assertion table(s)
112version/object relationship and physical
112Assertion time
64,
87–88,
192,
264–267,
294effective time and, asymmetry between
136withdrawing current assertion into closed, and superceding it
272fAssertion time period
124–125conventional tables and
125B
[Before] relationship
67,
312Begin date, time period, (bd)
,
in Asserted Versioning temporal model
64in standard temporal model
64Best practices
43versioning, scope and limits of
92–93"Between,"
58used in closed-open conventions
58Bi-temporal data
3–7,
3fmanagement methods, taxonomy of
27–46research and development, ongoing
394–396Bi-temporal tables
6f,
64,
355fconventional table and, RI constraints between
171–173conventional table into, transform
view on, assertion table
136Bi-temporality, concept of
63–65Asserted Versioning implementation of
122effective time versioning and
87–88,
93Business keys
122,
174asserted version tables and
116C
Change
versionable/non-versionable
100Clock tick duration (CTD)
333Column(s)
12in asserted version tables, role of
120Conventional databases
non-temporal and, distinguishing between
350–351Conventional table(s)
,
45–46,
75,
142,
262–267,
294assertion time period and
125basic version table and
77–79into bi-temporal table, transform
bi-temporal tables and, RI constraints between
171–173vs. logical delete version table
84–85objects represented in
77,
141update transaction, second
81fConventional transactions
143CREATE VIEW statements
296Cube explosion problem
18–19D
Data Definition Language (DDL)
370Deferred assertion(s)
44–45,
48,
65,
128–129,
143,
163–164,
192,
261–288,
262–267,
269–279current episode before
269fdelete transaction and
277effective time alignment
275fserialization property of
273,
277Deferred assertion group
281approval transaction applied to
283f,
284Delete
to temporal gap version table, applying
87Delete cascade, temporal
176Delete transaction
82–83,
82f,
106deferred assertions and
277logical delete version table after
84flogical delete versioning before
83ftemporal gap versioning table before/after
86f,
87ftemporal to physical mapping
154fDelete transaction, temporal
154–159,
209–211,
226–232first physical transaction
156first physical transaction, before/after
155f,
156fafter second physical transaction
158ftemporal to physical mapping
227fDeveloping Time-Oriented Database Applications in SQL (Snodgrass)
44E
Effective time
14,
111–112,
162,
192,
294assertion time and, asymmetry between
136relationships and temporal integrity constraints
194Effective time versioning
77,
87–91,
93after proactive insert transaction
88fretroactive inserts/deletes and
90–91,
91fretroactive updates and
89–90after three proactive transactions
89fEnd date, time period, (ed)
,
Enterprise contextualization
391Episode, current
before deferred assertion
269fdeferred update, example scenario
269–274effective time alignment
270fEpisode, shortening forwards
228–230Episodes, merging
220–222adjacent, after transaction
221f[Equal] relationship
67,
311Event temporal data
38–40vs. state temporal data
40–41Events
queryable temporal data and
37–41,
43things and, distinction between data about
37[Excludes] relationship
66,
67,
71F
First-order predicate logic (FOPL)
72First-order temporal logic (FOTL)
72Foreign key (FK)
12,
173existence dependency and
248relationships/constraints and
247–250G
Gap version table, temporal
delete transaction, before/after
86f,
87fGREATER THAN predicate
358H
Hierarchy
28,
30–31non-exclusive vs. exclusive
30History
of temporal data management
11–26I
Index(ing)
358,
364,
370asserted version tables, performance for
357bi-temporal tables using, performance tuning
352–371Information technology best practices
42Insert transaction
78f,
79–80,
115–116,
261effective time versioning after proactive
88feffective time versioning and, retroactive
90–91,
91fphysical transaction before/after
146ftemporal to physical mapping
145fvs. update transaction
107Integrity constraints
46effective time relationships and
194Integrity constraints, temporal
104–111effective time relationships and
194J
Jointly exhaustive rule
31–32L
Leaf node
29,
34of supplier, self, and customer
31Logical delete version table
after delete transaction
84fLogical delete versioning
77,
83–85before delete transaction
83fM
Managed objects, child
243–244parent and, relationship between
242Managed objects, parent
244–245child and, relationship between
242Management, temporal data
161–162concepts from Asserted Versioning
52–53Matching representation
108Materialized Query Tables (MQT)
376–377Mental model
144explicitly temporal transactions
195–197Metadata
168Asserted Versioning database from, generating
181–186Metric values of relationships
38Mutually exclusive rule
32–34N
Nine-Fold Way, mirror images of
307,
308fNon-metric relationships
40Non-temporal databases
conventional databases, distinguishing between
350–351O
Object(s)
48,
95–96,
97–104conventional table, inserted into
99conventional table, represented in
77,
141existence dependency between
171temporal delete transactions and
155time period as occupied by
144version, assertions, and, relationship between
194fversion table, represented in
77,
99versions and, relationship between
112[Occupies] relationship
67On-line analytical processing (OLAP)
18On-line transaction tables
13–14Operational data stores (ODS)
16,
17P
Partitioning
373–375Asserted Versioning strategy for
374Period 1
316[before] Period 2, inverse of relationship
329[during] Period 2, inverse of relationship
321[excludes] Period 2, inverse of relationship
331[fills] Period 2, inverse of relationship
324–325[intersects] Period 2, inverse of relationship
326–327[occupies] Period 2, inverse of relationship
322[overlaps] Period 2, inverse of relationship
341Physical data model (PDM)
168–169,
180–181Asserted Versioning database from, generating
181–186conventional logical data model into temporal, translating
169–181process by which, is generated
181sample database and notations
180f,
181Point in time 1
[before] Period 1, inverse of relationship
338–339[before] Point in time 2, inverse of relationship
341[meets] Period 1, inverse of relationship
339–340Preferred Provider Organization (PPO)
81Primary key (PK)
,
77,
173surrogate keys used as
105Proactive transaction, effective time versioning after three
89fProactive transactions
219Production queries
36,
96–97,
114Asserted Versioning and
115against Asserted Versioning database
387Q
Queries, writing
against physical tables
114R
Rational reconstruction
1–2Real-time data warehousing
18,
20Record-at-a-time operations
22–23Referential integrity, temporal (TRI)
46,
48,
96,
104,
108–111,
163,
191–192,
214,
384–385child/parent managed objects in, relationship
242,
243–244temporal delete transaction, applied to
254–259temporal insert transaction, applied to
253–254temporal transactions, applied to
253–259temporal update transaction, applied to
254version table view and
135Referential integrity (RI)
104,
108,
191–192,
244constraints between conventional/bi-temporal tables
171–173parent/child row, relationship between
242parent/child table and
104Referential relationships, mixed
172,
173Relational model
24,
52Asserted Versioning and
394Relational theory
95–96integrity constraints in
104Retroactive transactions
216Row(s)
12,
95–96with Asserted Versioning, creation of
125assertion tables, representation in
75child/parent relationships
108,
242delete cascade, level analysis of
255–259in empty assertion time
276to time, nine relationships of
265fversion tables, representation in
75S
Slowly changing dimensions (SCD)
18–19Standard temporal model
44,
64Star schema temporal data
396State(s)
queryable temporal data and
37–41,
43State temporal data
40–41vs. event temporal data
40–41State transformations, temporal extent
198,
199to asserted version tables
163Statements
264–267of Asserted Versioning, basic
97Stock-keeping unit (sku)
19Structures and processes of temporal data, encapsulation of
383–389Subtypes, exclusive/non-exclusive
31Surrogate keys
97asserted version tables and
116,
122T
Target range
222withdrawing version in
224fTarget span
206temporal insert transaction and
195–196for temporal transaction
195Target timespan
on temporal update transactions
208–209Taxonomy
27,
28–34,
28f,
197of bi-temporal data management methods
27–46among Information technology professionals
29management of temporal data, of methods for
34–46,
35ftemporal extent transformations
237,
238fTemporal delete transaction
Temporal extent state transformations
Temporal extent transformations
Temporal upward compatibility
69–70Things
97–98events and, distinction between data about
37Time
rows to, nine relationships of
265fTime period(s)
47,
56–63clock ticks, measured in
55effective time versioning and
87–88objects, as occupied by
144U
Universal Coordinated Time (UTC)
56,
62–63Update(s)
retroactive, effective time versioning and
89–90to uni/bi-temporal tables
7–8Update, deferred
277to current episode, example scenario
269–274deferred assertions and
277Update, temporal
195,
196vs. temporal extent transformations
222Update transaction
80–81,
80f,
81f,
106to asserted version table
113vs. insert transaction
107temporal to physical mapping
149fwith versioning, in place
102Update transaction, first temporal
physical transaction, after first
149fphysical transaction, after second
151fphysical transaction, after third
151fUpdate transaction, second temporal
152–154physical transaction, after second
153fphysical transaction, after third
154fphysical transaction, before/after first
152fphysical transaction, second
153Update transaction, temporal
147–152,
158,
206–209,
222–226physical transaction, before first
148fphysical transaction, second
150–151physical transactions, three types of
148temporal to physical mapping
223fin updating policy, replacing unaffected version
225fin updating policy, superceding affected versions
225fin updating policy, withdrawing version in target range
224fin updating policy before transaction
223fUser-defined properties (UDPs)
169,
182V
Validity checks
201temporal delete transaction
209Version(s)
,
48,
95,
96,
97–104assertions, objects, and, relationship between
194fobjects and, relationship between
112Version table(s)
43objects represented in
77,
99Version table, basic
conventional table and
77–79insert transaction
78f,
79update transaction, second
81fVersion table view
134–135effective begin date in
134Versioning
43,
52,
77best practice, scope and limits of
92–93update transaction in place with
102W
WHERE clause predicate
64,
86
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.