Index
Note: Page numbers followed by f indicate figures.
A
Accessibility, temporal data
11, 21
Acyclic relationships
28
[Aligns] relationship
67
Allen relationship(s)
47–48, 65–68, 70, 106, 174, 233, 311–348, 346–347
AVF, used by
312
completeness check
233–237
expression of
346–347
four categories
67–68
taxonomy
66f, 197–198, 234f, 312f
temporal delete transaction and
235, 236, 237
temporal insert transaction and
235
V_Allen_Example to illustrate
315–316
Allen relationship queries
313–342
claims processing example
343–346
point in time to period of time
333–341
point in time to point in time
341–342
time period to time period
316–332
Alternative temporal model
41–43
API Call
113
to AVF
386
Approval transaction
280–284
assertion dates on
282
deferred assertion group, applied to
283f, 284
Archives
396
As-is
distinction
100–101
history
301
report
6, 93, 298
table
301
Asserted version rows
96, 142
circa flag and
360
example of notation describing
131
Asserted version table(s)
102–103, 120f, 167, 382, 383
Allen relationship queries against
313–342
business keys and
116
column sequencing for
359
columns, role of
120
with example
120–125
index performance for
357
maintenance to
145–159, 163
oid in
122
query, how to
164
query, through views
133
sample
131f
surrogate keys and
116, 122
temporal extent state transformations to
163
temporal transaction against
137, 163
update transaction to
113
views and
132–137
Asserted version tables, basic diagram of
126f, 130
five main components
130
how to read
125–130
Asserted Versioning
2, 24, 27, 47, 97, 161–162, 261–262, 390
Allen relationship taxonomy
66f
assertion begin dates
128
basic statement of
97
beliefs
265
as bridge
392–394
business key, use of term
174
computer research and, origins of
51–74, 54–72
core concepts of
95–118
design encapsulation
169
as destination
392–394
in Information technology best practices
48, 75–94
as leaf node
34
machinery of
120
managed objects of
95, 197
management
111
managing power of
52
metadata
173–180
non-unique PKs
366–368
ontology
394
optimize
164–165
origins of
51–54, 54f, 75–94
partitioning strategy for
374
pipeline datasets and
308–309
practical orientation of
53–54
production queries and
115
query performance in
390–391
relational model and
394
row, creation of
125
TEI and
123
temporal data, approach to
43
temporal data management and
52–53
temporal model
44–46, 64, 192, 381–382
temporal transactions
200–211
Asserted Versioning, implementation of
352
bi-temporality
122
enterprise
122
Asserted Versioning databases
167, 173, 186
ad hoc queries against
387–388
designing
167–190, 168f
optimizing
349–380
production queries against
387
Asserted Versioning Framework (AVF)
45, 53, 61, 113, 169–170, 191, 213, 222, 387
Allen relationship used by
312
API Call to
386
constraints, enforcement of
191–192
deferred transactions workflow management and
394
episode begin date, determining
220
row withdrawals
360, 361
TFK and
248–249
TRI, enforcement of
109
TRI enforcement code
368
validity checks and
201–203, 206–208, 209
Asserted Versioning schema
apparent redundancies in
186–188
bi-temporal, redundancies in
186–189
evolution
104
real redundancies in
188–189
Assertion(s)
48, 95, 97–104, 300
currency flags and
359
locked
284
past-dated
135–136
series of
103
vs. statements
263–267
terminate
125
version, objects, and, relationship between
194f
Assertion begin date (Asr-beg)
64, 103–104, 121, 143
Asserted Versioning model
128
future
65
standard temporal model
128
Assertion end date (Asr-end)
61–62, 103–104, 121, 150, 359
arguments of redundancy
186, 187–188
in index
358
non-12/31/9999
150
Assertion table(s)
112
row representation in
75
uni-temporal
41, 111–112, 142
version/object relationship and physical
112
Assertion time
64, 87–88, 192, 264–267, 294
closed
271–272
constraint
194
current
276–277, 360
deferred, semantics of
262–267
within effective time
192–195
effective time and, asymmetry between
136
far future
279–284, 306
future
162, 381–382
granularity
173, 174
history, example of
157–158
movements
284
near future
279–284, 306
past
297, 360, 361
present
298
shared
194
snapshots
126–127, 129
tag
194
withdrawing current assertion into closed, and superceding it
272f
Assertion time period
124–125
behavior
145
conventional tables and
125
default
215
Associative table
39, 251, 252
temporal transactions and
250–252
As-was
101
distinction
100–101
history table
301
report
6, 93, 298
table
301
B
Backups
13, 21, 295
Balance records
39
Balance tables
38–40
Balanced tree (B-tree)
352–353
index
353
Basic scenario
48–49, 115, 141–160, 142–143
maintaining asserted version table
145–159
temporal delete transaction
154–159
temporal insert transaction
145–147
temporal update transaction
147–154
Batch transaction
datasets
281
[Before] relationship
67, 312
Begin date, time period, (bd)
3, 4
in Asserted Versioning temporal model
64
clock ticks and
55
in standard temporal model
64
Beliefs, terminology of
264–265
Best practices
43
versioning, scope and limits of
92–93
"Between,"
58
inclusive sense of
58
used in closed-open conventions
58
Bi-temporal data
3–7, 3f
ad hoc queries against
382–383
full-range
114–115
management methods, taxonomy of
27–46
nine categories of
382, 389, 390
research and development, ongoing
394–396
seamless access to
24, 97, 114–115
semantic constraints
383–384
state
41–46
structure
7
Bi-temporal databases
data volumes
350–351
response times in
350–351
Bi-temporal match logic
115–116
Bi-temporal tables
6f, 64, 355f
B-tree index for
353
with circa flags
362f
conventional table and, RI constraints between
171–173
conventional table into, transform
7
performance tuning
352–371, 372–378
physical
27
query writing against
114–115
updates to
7–8
view
142
view and, non-bi-temporal
111–115
view on, assertion table
136
Bi-temporal theory
171–172
Bi-temporality, concept of
63–65
Asserted Versioning implementation of
122
effective time versioning and
87–88, 93
Business data
121
processing
11
type
121
Business key metadata
176–177
table
176f
Business keys
122, 174
asserted version tables and
116
conventional tables and
115–116
examples
177
missing or incomplete
174
reliable/unreliable
201
uniqueness
177
Business rules
384–385
C
Change
tracking
37–38
versionable/non-versionable
100
Child nodes
28, 29, 31–32
jointly exhaustive
31–32
mutually exclusive
32–34
Chronon
47, 55
Circa flag
360, 361–362, 375–376
bi-temporal table with
362f
purpose of
364
queries and, performance of
364–365
update process
361, 364
uses of
364–366
Client
table
242
as TFK
121
Clock tick(s)
47, 55–56, 216
atomic
47, 55, 79–80, 174
begin date/end date
55
box
127
convention/constraint
106–108
defined
55
gap
216
granularity
55, 173, 174, 333
limitations
79–80
time periods measured in
55
Clock tick duration (CTD)
333
see alsofCTD
Clocks
55–56
Closed-open convention
124–125, 333
"between" used in
58
time period representations
57–59, 57f
Clustering
375–376
CODASYL network model
24
Codd, E. F
24
Codd, Ted
22
Column(s)
12
in asserted version tables, role of
120
level versioning
100–102
match
355
PK
4
position
357
sequencing
353–354, 356–357, 358, 359
Completeness checks
233–238
Allen relationship
233–237
temporal extent transformations
237–238
Conform(ed)
17–18
data
18
dimensions
17–18
Conventional data
2, 3–7, 3f, 163
PK
3
rows
46, 76, 192, 192f
view
388
Conventional databases
data volumes
350–351
non-temporal and, distinguishing between
350–351
response times in
350–351
Conventional table(s)
3, 45–46, 75, 142, 262–267, 294
assertion time period and
125
basic version table and
77–79
into bi-temporal table, transform
7
bi-temporal tables and, RI constraints between
171–173
business keys and
115–116
customer
3, 41
delete transaction
82f, 210
EI with
105
insert transaction
78f, 79, 105, 203
vs. logical delete version table
84–85
objects inserted into
99
objects represented in
77, 141
surrogate keys and
115–116
update transaction
80f, 208
update transaction, second
81f
versioning
43
Conventional table view
112–113, 133
DDL
133
example
133f, 134f
Conventional transactions
143
CREATE VIEW statements
296
Cube explosion problem
18–19
Currency flags
359–360
to optimize queries
360–364
versions/assertions and
359
Current data
12, 62, 76, 301–303, 302f
paradigm used to access
23
view
302, 303
Customer
29, 30, 31–32
leaf node of
31
reports
6
Customer table
30
conventional
3, 41
uni-temporal
4
versioned
4
D
Darwen, Hugh
41–42
Data cubes
18–19
OLAP
18
Data Definition Language (DDL)
370
Data marts
1–2, 14–15
dimensional
16
fact/dimension
39
vs. warehouse
15, 16–18
Data modelers
53–54, 168, 384
Data structures
181
developer-designed
12
Data warehouse
1–2, 13, 14–15
vs. data mart
15, 16–18
historical
16
project
16
Database management systems (DBMS)
12, 22, 24, 55, 127–128, 169–170
archives
294–295
enforcement of constraints
191–192
FK and
248–249
limitations
374
relational
22, 24
TFK and
178
timestamps
59
Dataset
267
Date
formats for date literals
333, 334f
pairs
56–63
unknown
60
Date, Chris
41–42
Daylight Savings Time
62
DB2
62
Deferred assertion(s)
44–45, 48, 65, 128–129, 143, 163–164, 192, 261–288, 262–267, 269–279
approving
280–284
current episode before
269f
deferred update to, example scenario
274–275, 278–279
delete transaction and
277
effective time alignment
275f
far future
279–284, 306
locking associated with
272–273
near future
279–284
serialization property of
273, 277
TRI and
284–285
update and, deferred
277
use of
53
withdrawing
278f
Deferred assertion group
281
approval transaction applied to
283f, 284
Deferred transaction(s)
44–45, 48, 128, 192, 262, 267
locking associated with
272–273
use of
53
workflow management and AVF
394
Delete
cascade
176
logical
77
physical
77
proactive
87
retroactive
90–91
rule indicator
176
to temporal gap version table, applying
87
Delete, temporal
195, 196
rule used from parent
370
scope of
210
target range
227
target span and
196
TRI enforcement
371
Delete cascade, temporal
176
row-level analysis of
255–259
transaction, before/after
256f, 257f
TRI after
259f
Delete options, temporal
252–253
CASCADE
252–253, 366, 370
RESTRICT
252–253, 255, 366, 370
SET NULL
252–253, 366, 370
Delete transaction
82–83, 82f, 106
conventional table
82f, 210
deferred assertions and
277
logical delete version table after
84f
logical delete versioning before
83f
proactive
89
scope of
210
sequence of
142
temporal gap versioning table before/after
86f, 87f
temporal to physical mapping
154f
Delete transaction, temporal
154–159, 209–211, 226–232
Allen relationship and
235, 236, 237
basic scenario
154–159
episodes and
155
first physical transaction
156
first physical transaction, before/after
155f, 156f
format of
209
mechanics
210–211
objects and
155
second physical transaction
157–159
after second physical transaction
158f
semantics
210
temporal to physical mapping
227f
TRI applied to
254–259
validity checks
209
Design encapsulation
169, 383, 384–386
Developing Time-Oriented Database Applications in SQL (Snodgrass)
44
Devlin, Barry
13
Diagrams
119–140
notations and
130–132
Disk
storage
13
Domain integrity (DI)
104
Duplicate report
101
E
Edit checks
201
Effective begin date (Eff-beg)
120–121, 357
defaults
201
specified
137
in version table view
134
Effective end date (Eff-end)
121, 128, 357, 359
arguments of redundancy
186, 186–187
defaults
201
specified
137
in version table view
134
Effective time
14, 111–112, 162, 192, 294
within assertion time
192–195
assertion time and, asymmetry between
136
containment
194
diagram
130f
granularity for
173
past
297, 298
present
298
relationships and temporal integrity constraints
194
span
252
Effective time alignment
270–271, 275f
current episode
270f
Effective time period
124
default
215
notations
131
Effective time versioning
77, 87–91, 93
bi-temporality and
87–88, 93
after proactive insert transaction
88f
retroactive inserts/deletes and
90–91, 91f
retroactive updates and
89–90
scope and limits of
93
after three proactive transactions
89f
time period and
87–88
Encapsulation concept
53
End date, time period, (ed)
3, 4
clock ticks and
55
non-12/31/999
61
12/31/9999
86–87, 206
Enterprise contextualization
391
Entity integrity (EI)
104, 146, 191–192
with conventional table
105
vs. TEI
105
Episode
45–46, 48, 51–52, 95–96, 97–104, 143
affected by update/delete
196
closing open
157
concept of
315
datatype
315
expand existing
107
"filling in gap" between
147
open
204
parent
243, 245, 368–369
queries about
312–313
rows and
99–100
shortening backwards
230–231
single-version
217
temporal delete transactions and
155
views
315, 388
waking up closed
206
Episode, creating
216–217
transaction, before/after
216f, 217f
Episode, current
before deferred assertion
269f
deferred update, example scenario
269–274
effective time alignment
270f
Episode, deleting
227–228, 228f
before transaction
227f
Episode, lengthening backwards
215, 217–219
after transaction
218f
Episode, lengthening forwards
215, 219–220
transaction, before/after
219f, 220f
Episode, shortening forwards
228–230
after step 1
229f
after step 2
230f
Episode, splitting
231–232
after step 1
232f
after step 2
232f
Episode begin date (Epis-beg)
121, 124, 147, 188
AVF determining
220
Episodes, merging
220–222
adjacent, after transaction
221f
[Equal] relationship
67, 311
EQUALS predicate
357
Error
correction
42
off-by-one
22–23
ERwin
data modeling tool
169
UDPs
169, 182
Event temporal data
38–40
vs. state temporal data
40–41
Events
features of
38
vs. objects
98
queryable temporal data and
37–41, 43
represented in table
98
things and, distinction between data about
37
[Excludes] relationship
66, 67, 71
Existence dependency
108, 242
FK and
248
between objects
171
TFK and
174–175
Extracts
268
F
Factual claims
294
Feeds
268
File access methods
22
[Fills] relationship
66–67, 312, 322
First-order predicate logic (FOPL)
72
First-order temporal logic (FOTL)
72
Foreign key, temporal (TFK)
104, 109, 123–124, 147–148, 243–245, 368
AVF and
248–249
client as
121
constraints
247–250
date value/function value
249–250
DBMS and
178
delete indicator for
176
existence dependency and
174–175
vs. FK
175
indexes
371
metadata
174–176, 246
metadata table
175f, 177f
relationships
245, 247–250
required/not required
175–176
at schema level
123
TRI enforcement on
370
TRI with multiple
251–252
Foreign key (FK)
12, 173
DBMS and
248–249
existence dependency and
248
lost information
178
mapping metadata
177–178, 177f
relationships/constraints and
247–250
temporalized
52
vs. TFK
175
TRI
71
fCTD
333, 334
G
Gap version table, temporal
delete to, applying
87
delete transaction, before/after
86f, 87f
Gap versioning, temporal
77, 85, 86–87, 93
scope and limits of
92–93
Gaps, temporal
85
getdate()
62
Granularity
173, 333
assertion time
173, 174
clock tick
55, 173, 174, 333
effective time
173
mismatch issues
174
GREATER THAN predicate
358
H
Hibernate
395
Hierarchy
28, 30–31
non-exclusive vs. exclusive
30
partitioned semantic
34
of role/types
31
Historical data
76
access to
16
accommodating
23
backed-up, access to
21
manifestation of
1
warehouse
16
Historical databases
13
History
as-is
301
assertion time, example of
157–158
state-based
40
of temporal data management
11–26
History, Current
300–301, 300f
view
300
History, Pending
304–305, 304f
History, Posted
297–298, 297f
datasets
301
pipeline dataset
292
view
297
History tables
13–14, 53, 300–301
as-was
301
logged time
41–42
vs. transaction table
13–14
I
Index(ing)
358, 364, 370
advanced strategies
68–69
asserted version tables, performance for
357
assertion end date in
358
bi-temporal tables using, performance tuning
352–371
B-tree
353
column sequencing in
353–354, 356–357, 358, 359
currency flags and
359–360
design
353–354
methods
68–69
objective for
360
of parent table
366–367
partitioning
374
queries, to optimize
354–366
scan
353, 356, 363
temporalized unique
395
TFK
371
on time periods
70
traditional
68
tree
355
TRI, to optimize
366–371
on TRI child
370–371
on TRI parents
368–370
Indexed Views
376
Information technology best practices
42
Asserted Versioning in
48, 75–94
Inmon, Bill
14–15, 17–18
vs. Kimball
16–18
Insert, temporal
195, 205
example
205
scope of
204
Insert transaction
78f, 79–80, 115–116, 261
conventional table
99, 105, 203
effective time versioning after proactive
88f
effective time versioning and, retroactive
90–91, 91f
intersection of
146
physical transaction before/after
146f
scope of
204
sequence of
142
surrogate key and
97
temporal to physical mapping
145f
vs. update transaction
107
versioning, basic
79–80
Insert transaction, temporal
107–108, 145–147, 201–206, 214–222
Allen relationship and
235
basic scenario
145–147
example of
216
format of
201
mechanics
204–206
results in
147
semantics
203–204
target span and
195–196
temporal to physical mapping
215f
TRI applied to
253–254
validity checks
201–203
Integrity constraints
46
effective time relationships and
194
encapsulation of
45
enforcement of
191–192
in relational theory
104
simplification of
45–46
Integrity constraints, temporal
104–111
AVF enforcement of
191–192
effective time relationships and
194
[Intersects] relationship
66–67, 312
IS-A relationship
29
J
Java
395
Johnson, Samuel
37
Jointly exhaustive rule
31–32
K
Kimball, Ralph
15, 17–18, 19, 39
vs. Inmon
16–18
KIND-OF links
29
L
Leaf node
29, 34
of supplier, self, and customer
31
Links
29
Linnaeus, Carl
28
Logfiles
21, 295
physical
389–390
semantic
389
view, semantic
388
Logic, temporal
72
Logical data model (LDM)
167–168, 169–171, 173, 186
sample database
170f
into temporal physical data model, translating
169–181
Logical delete version table
conventional table
84–85
after delete transaction
84f
Logical delete versioning
77, 83–85
before delete transaction
83f
scope and limits of
92
Loop coding
22–23
Lorentzos, Nikos
41–42
M
Macro structures
2
Maintenance encapsulation
383–384, 386–387
Managed objects
95, 141, 143, 248
of Asserted Versioning
95, 197
vs. object
141–142
RI/TRI and
242
Managed objects, child
243–244
parent and, relationship between
242
in TRI relationship
242, 243–244
Managed objects, parent
244–245
child and, relationship between
242
in TRI relationship
242, 244
Management, temporal data
161–162
complexities
7–8
concepts from Asserted Versioning
52–53
history of
11–26
levels of
13, 34–35
in 1980s
13–14
in 1990s
14–18
taxonomy of methods for
34–46, 35f
in 2000s
18–20
Mart
Match columns
355
Match logic
116
bi-temporal
115–116
Match predicate flags
360
Matching predicates, direct
355, 356, 359
Matching representation
108
Materialized Query Tables (MQT)
376–377
MAX(dt) predicates
372
[Meets] relationship
67
Mental model
144
explicitly temporal transactions
195–197
Metadata
168
Asserted Versioning
173–180
Asserted Versioning database from, generating
181–186
FK mapping
177f
miscellaneous
178–180, 178f
tables
385
temporal
169
TFK table
175f, 177f
Metric values of relationships
38
Micro-level structures
2
“mmmyy” representation
78
Murphy, Paul
13
Mutually exclusive rule
32–34
relaxing
33
violating
33
N
Nine categories of temporal data
264–267, 265f, 293f, 294–295, 382
Nine-Fold Way, mirror images of
307, 308f
Nodes
28
relationship between
29
Non-metric relationships
40
Non-temporal data
Non-temporal databases
conventional databases, distinguishing between
350–351
data volumes
350–351
response times in
350–351
Non-temporal tables
Notations
119–140, 131
forms of
131–132
in-line
132
new diagrams and
130–132
PDM sample database and
180f, 181
Now()
62–63, 133, 264
NULL
60
vs. 12/31/9999
372–373
O
Object(s)
48, 95–96, 97–104
child/parent, relations
108–109, 366
contiguous
106
conventional table, inserted into
99
conventional table, represented in
77, 141
vs. events
98
existence dependency between
171
vs. managed objects
141–142
non-contiguous
106
queryable
296–307
representation of
48–49, 98
rows and
141
same
85
static
98
temporal delete transactions and
155
in time period, representation of
142–144, 143f, 195
time period as occupied by
144
version, assertions, and, relationship between
194f
version table, represented in
77, 99
versions and, relationship between
112
Object identifier (oid)
109, 120, 214, 222, 366–367
in asserted version table
122
combinations of
201
Objects, persistent
40, 43, 97, 161–162
features of
38
[Occupies] relationship
67
On-line analytical processing (OLAP)
18
On-line transaction tables
13–14
Open/closed combinations
199–200
Operational data stores (ODS)
16, 17
Overwritten data
89
reasoning for
89–90
P
Parent nodes
28, 29
Partition(ed)
29
defining
374–375
semantic hierarchy
34
semantic trees
28–31
Partitioning
373–375
Asserted Versioning strategy for
374
by date
373
index
374
by known field
373–374
by random field
374
Performance tuning
351–352, 390–391
bi-temporal tables, other techniques
372–378
bi-temporal tables using indexes
352–371
general considerations
353–354
standard techniques
377–378
Period 1
316
[aligns] Period 2
319–320, 319f
[before] Period 2
328–329, 328f
[before] Period 2, inverse of relationship
329
[during] Period 2
320–321, 320f
[during] Period 2, inverse of relationship
321
[equals] Period 2
323, 323f
[excludes] Period 2
331–332, 331f
[excludes] Period 2, inverse of relationship
331
[fills] Period 2
324–325, 324f
[fills] Period 2, inverse of relationship
324–325
[finishes] Period 2
317–319, 318f
[intersects] Period 2
326–328, 327f
[intersects] Period 2, inverse of relationship
326–327
[meets] Period 2
329–331, 330f
[occupies] Period 2
321–323, 322f
[occupies] Period 2, inverse of relationship
322
[overlaps] Period 2
325–326, 325f
[overlaps] Period 2, inverse of relationship
341
[starts] Period 2
316–317, 317f
Period 2
316
see alsoPeriod 1
PERIOD datatype
70–71, 135, 177, 297–298, 315, 346–347
user-defined
347
Physical data model (PDM)
168–169, 180–181
Asserted Versioning database from, generating
181–186
conventional logical data model into temporal, translating
169–181
process by which, is generated
181
sample database and notations
180f, 181
temporalization process
182–185
Pipeline dataset(s)
48, 163, 261–288, 268, 289, 295
Asserted Versioning and
308–309
categories of
164, 296
inflow
52–53
managing
308
nine temporal combinations
293f
outflow
52–53
pending projections
292
physically distinct
290–291, 290f
Posted History
292
as queryable objects
296–307
Pipeline datasets, internalized
52–53, 267–269, 281, 291, 291f, 292–296, 389–390
re-presenting
289–310
value of
308–309
Pipelines
concept of
268
data
269
inflow
268
lost data and
295–296
outflow
268
Point in time, queries
382–383
to Period of time
333–341
to Point in time
341–342
Point in time 1
[before] Period 1
338–339, 339f
[before] Period 1, inverse of relationship
338–339
[before] Point in time 2
341, 342f
[before] Point in time 2, inverse of relationship
341
[during] Period 1
336–337, 337f
[equals] Point in time 2
342, 343f
[excludes] Period 1
340–341, 341f
[finishes] Period 1
335–336, 336f
[meets] Period 1
339–340, 340f
[meets] Period 1, inverse of relationship
339–340
[meets] Point in time 2
342, 342f
[occupies] Period 1
337–338, 338f
[starts] Period 1
334–335, 335f
Post-date
epistemologically
45
ontologically
45
Preferred Provider Organization (PPO)
81
Primary key (PK)
3, 77, 173
of asserted version table
147, 367–368
bi-temporal data
4–5, 72
columns
4
conventional data
3
non-unique
366–368
physical/logical
367
surrogate keys used as
105
Proactive transaction, effective time versioning after three
89f
Proactive transactions
219
Production
database
267–268
datasets
267–268
Production queries
36, 96–97, 114
Asserted Versioning and
115
against Asserted Versioning database
387
Production table
163, 267–268, 291–292
data extracted from
268
pipeline data flowing towards
269
Projections, current
303–304, 303f
view
304
Projections, pending
306–307, 306f
pipeline datasets
292
Projections, posted
299–300, 299f
view
299
Q
Queries
23–24, 301, 311–348, 312–313, 353, 383
about episodes
312–313
asserted version tables, how to
164
asserted version tables through views
133
authors
53–54
circa flag and performance of
364–365
currency flags to optimize
360–364
encapsulation
96, 384, 387–389
indexes to optimize
354–366
performance
390–391
result sets
268
Queries, writing
against bi-temporal tables
114–115
against physical tables
114
Queryable temporal data
35, 36–37, 161–162, 391
events and states
37–41, 43
R
Range predicate
356
Rational reconstruction
1–2
Real-time data warehousing
18, 20
Reconstructable temporal data
35, 36, 161–162, 391
Record-at-a-time operations
22–23
Referential integrity, temporal (TRI)
46, 48, 96, 104, 108–111, 163, 191–192, 214, 384–385
see alsofTRI
AVF enforcement of
109, 368
basic diagram
243f, 245–247
checks
371
child, indexes on
370–371
child table
249
child/parent managed objects in, relationship
242, 243–244
child-side
109
concept of
385
constraints
111, 181, 185–186, 241–242
deferred assertions and
284–285
after delete cascade
259f
delete enforcement
371
dependency
171
enforcement
189, 366, 368
FK
71
indexes to optimize
366–371
managed objects and
242
parent table
249
parent/child relationship
371, 383–384
parents, index on
368–370
parent-side
110–111
relational rule
108
relationships
109, 147–148, 171, 243
temporal delete transaction, applied to
254–259
temporal insert transaction, applied to
253–254
temporal transactions, applied to
253–259
temporal update transaction, applied to
254
TFK, enforcement on
370
TFKs, with multiple
251–252
validation check
250
version table view and
135
violations
108–109, 110
Referential integrity (RI)
104, 108, 191–192, 244
constraints between conventional/bi-temporal tables
171–173
dependency
171
managed objects and
242
parent/child row, relationship between
242
parent/child table and
104
relationship
171, 241–242
Referential relationships, mixed
172, 173
Regulatory agency
31–32
Relational model
24, 52
Asserted Versioning and
394
rows
95
Relational technology
3
Relational theory
95–96
integrity constraints in
104
Reliability of data
33
Research and development
54–72, 394–396
Asserted Versioning and, origins of
51–74, 54
Retroactive transactions
216
Root node
35–37
Row(s)
12, 95–96
with Asserted Versioning, creation of
125
assertion tables, representation in
75
AVF withdrawals
360, 361
bi-temporal tables
75–76, 193, 193f
child/parent relationships
108, 242
conventional data
46, 76, 192, 192f
conventional table
95, 171–172, 192, 263
delete cascade, level analysis of
255–259
in empty assertion time
276
episode and
99–100
inserting
261
level versioning
100–102
locked
149
number
120
objects and
141
relational model
95
state temporal data
40
to time, nine relationships of
265f
version tables, representation in
75
withdrawn
126–127
Row creation date (Row-crt)
64, 121, 125, 148
arguments of redundancy
186, 188
Row-level warehousing
S
Screens
268
Seamless access, bi-temporal data
24, 97, 114–115
Seamless access, temporal data
20–24, 381–383
closing in on
22–24
objective for
21
performance aspect of
21–22
real-time
21, 24
usability aspect of
21–22
Self
29, 30
leaf node of
31
Slowly changing dimensions (SCD)
18–19
limitations of
20
Snapshot
assertion time
126–127, 129
paradigm
20
Snodgrass, Rick
14, 24, 43, 44, 54, 69, 385
SQL
44, 136, 177, 347
BETWEEN
58
language
43, 346–347
Server
62, 86, 127–128
standards
69, 70, 72
temporal extensions to
14, 69–72
timestamps
56
transaction
163
view
135
SQL, Temporal (TSQL)
44
SQL3
69
Staging area views
388
Standard temporal model
44, 64
assertion begin date
128
begin date
64
Star schema temporal data
396
State(s)
bi-temporal data
41–46
history based on
40
queryable temporal data and
37–41, 43
uni-temporal data
41–46
State temporal data
40–41
vs. event temporal data
40–41
rows
40
State transformations, temporal extent
198, 199
to asserted version tables
163
possible scenarios
199–200
Statements
264–267
of Asserted Versioning, basic
97
vs. assertions
263–264
CREATE VIEW
296
time, assertions and
264–267
Stock-keeping unit (sku)
19
Stonbraker, Michael
22
Stovepipe data
17
Stovepipes, data
17
Structures and processes of temporal data, encapsulation of
383–389
Subtypes, exclusive/non-exclusive
31
Superscript
129–130
Supplier
29, 30, 31–32
leaf node of
31
Surrogate keys
97
asserted version tables and
116, 122
bi-temporal match logic and
115–116
conventional tables and
115–116
match logic
116
used as PK
105
T
Table type metadata
173–174, 175
table
173f
Target range
222
temporal delete
227
temporal update
223
withdrawing version in
224f
Target span
206
interpretation of
204
temporal delete and
196
temporal insert transaction and
195–196
for temporal transaction
195
temporal update and
196
Target timespan
default
215
on temporal update transactions
208–209
Taxonomy
27, 28–34, 28f, 197
Allen relationship
66f, 197–198, 234f, 312f
biological
28
of bi-temporal data management methods
27–46
among Information technology professionals
29
management of temporal data, of methods for
34–46, 35f
root node of
35–37
temporal extent state transformations
197–200, 198f, 221–222, 233
temporal extent transformations
237, 238f
Temporal delete transaction
Temporal entity integrity (TEI)
46, 48, 96, 104–108, 191–192, 214
Asserted Versioning and
123
conflict
146
constraints
181, 185–186, 204, 241
vs. EI
105
role of
105
version table view and
134–135
Temporal extent state transformations
Temporal extent transformations
completeness check
237–238
taxonomy
237, 238f
vs. temporal update
222
Temporal primary key (TPK)
71–72, 122–123
Temporal SQL (TSQL)
44
Temporal transactions
113, 123, 137–138, 142, 191, 200f, 265
against asserted version tables
137, 163
Asserted Versioning
200–211
associative tables and
250–252
basic
142, 143, 163
basic, mental model
144
edit checks
201
introduction to
191–212
mental model
195–197
on multiple tables
241–260
vs. physical
45, 53
on single tables
213–240
target span for
195
TRI applied to
253–259
TRI constraints and
241–242
validity checks
201
Temporal upward compatibility
69–70
Things
97–98
events and, distinction between data about
37
kinds of
95
Time
alignment
271
assertions, statements and
264–267
logical vs. physical
14
rows to, nine relationships of
265f
transaction
64, 87–88, 261
zone
62
Time period(s)
47, 56–63
clock ticks, measured in
55
closed-closed representation
57–58, 57f, 58–59
closed-open representation
57–58, 57f, 58–59
effective time versioning and
87–88
gap in time between
174
index on
70
non-contiguous
233–234
notations
131
object in, representation of
142–144, 143f, 195
objects, as occupied by
144
reducing
110
transaction
145
Time period, queries
Point in time to
333–341
to Time period
316–332
Timestamps
current
62
DBMS
59
SQL
56
Transaction
38–39
Transaction table
98, 267–268
vs. history tables
13–14
on-line
102
Tree structure
28
Triggers
395
12/31/9999
59–62, 127–128, 150
end date
86–87, 206
vs. NULL
372–373
U
Ubiquitous paradigm
12
Unique identifier (id)
3, 122, 174, 370
Uni-temporal data
3–7, 3f
state
41–46
term
4
Uni-temporal tables
4f
assertion
41, 111–112, 142
customer
4
updates to
7–8
version
41, 111, 142
Universal Coordinated Time (UTC)
56, 62–63
adjustment of
56
Update(s)
performance issue
358
in place
76
retroactive, effective time versioning and
89–90
to uni/bi-temporal tables
7–8
Update, deferred
277
to current episode, example scenario
269–274
to deferred assertion, example scenario
274–275, 278–279
deferred assertions and
277
temporal
270
Update, temporal
195, 196
deferred
270
limitations
226
target range
223
target span and
196
vs. temporal extent transformations
222
Update transaction
80–81, 80f, 81f, 106
to asserted version table
113
vs. insert transaction
107
proactive
89
second
81–82, 81f
sequence of
142
temporal to physical mapping
149f
with versioning, in place
102
Update transaction, first temporal
physical transaction, after first
149f
physical transaction, after second
151f
physical transaction, after third
151f
Update transaction, second temporal
152–154
physical transaction, after second
153f
physical transaction, after third
154f
physical transaction, before/after first
152f
physical transaction, first
152–153
physical transaction, second
153
physical transaction, third
153–154
Update transaction, temporal
147–152, 158, 206–209, 222–226
basic scenario
147–154
format of
206
mechanics
208–209
physical transaction, before first
148f
physical transaction, first
149–150
physical transaction, second
150–151
physical transaction, third
151–152
physical transactions, three types of
148
semantics
208
target timespan on
208–209
temporal to physical mapping
223f
TRI applied to
254
in updating policy, replacing unaffected version
225f
in updating policy, superceding affected versions
225f
in updating policy, withdrawing version in target range
224f
in updating policy before transaction
223f
validity checks
206–208
Updates, pending
305–306, 305f
Updates, posted
298, 298f
view
298
User-defined properties (UDPs)
169, 182
V
Valid time
Validity checks
201
temporal delete transaction
209
temporal insert transaction
201–203
temporal update transaction
206–208
TRI
250
V_Allen_Example
315–316
ver_end
86
Version(s)
4, 48, 95, 96, 97–104
assertions, objects, and, relationship between
194f
child
243, 245
currency flags and
359
dates
85
objects and, relationship between
112
overlapping
7–8
replacing unaffected
225f
superceding affected
225f
tables
13–14
uni-temporal
192–193, 193f
view, current
388
withdraw
224f
Version table(s)
43
customer
4
objects represented in
77, 99
physical
112
row representation in
75
uni-temporal
111
Version table, basic
conventional table and
77–79
delete transaction
82f
insert transaction
78f, 79
update transaction
80f
update transaction, second
81f
Version table view
134–135
effective begin date in
134
effective end date in
134
example
135f
sample
314–315
TRI/TEI and
134–135
Versioning
43, 52, 77
best practice, scope and limits of
92–93
conventional table
43
objections to
102
row-level vs. column-level
100–102
update transaction in place with
102
Versioning, basic
77, 79–83
delete transaction
82–83
insert transaction
79–80
scope and limits of
92
update transaction
80–81
update transaction, second
81–82
Views
111, 113, 114, 115
asserted version tables and
132–137
assertion table
135–137
benefits provided by
113
bi-temporal table
136, 142
conventional data
388
current data
302, 303
current version
388
episode
315, 388
history
297, 300, 304–305
Indexed
376
mental images and
137–138
non-bi-temporal, and bi-temporal tables
111–115
projection
299, 304, 306–307
query asserted version table through
133
semantic logfile
388
SQL
135
staging area
388
transaction file
388
update
298, 305–306
W
Warehouse
WHERE clause predicate
64, 86
X
xref table
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset