Map
Index
Random
Help
Topics
th

Topic: persistent data structure

topics > computer science > data > Group: data structures



Group:
data type
Group:
data value
Group:
database
Group:
variables

Topic:
archives
Topic:
frozen representation
Topic:
configuration management
Topic:
immutable files and data
Topic:
input/output by accessing a variable
Topic:
object-oriented databases
Topic:
object serialization
Topic:
read-only and write-once file systems
Topic:
running programs in a workspace or environment
Topic:
save-restore
Topic:
temporal database
Topic:
temporal relationships
Topic:
version control
Topic:
XML data type

Summary

A persistent data structure records current and historical values of a data structure. Non-volatile data is sometimes called persistent data. (cbb 1/90)
Subtopic: persistence up

Quote: people are expected to remember past values of attributes [»adamEN1_1973]
Quote: do not lose information [»cbb_1990, OK]

Subtopic: persistence and type up

Quote: as persistent storage, files cannot contain pointers nor carry their own types [»buneP5_1986]
Quote: while a value persists, so should its description (type); avoids round-trip errors
Quote: a data model should treat persistence, sharing and structure independently [»balzRM_1986]
Quote: a value's persistence should be independent of its type [»atkiMP6_1987]
Quote: persistence is a property of values not types [»buneP5_1986]
Quote: associate persistence with values and separate type from extent; e.g., the integer extent is almost useless; may want multiple extents [»buneP5_1986]
Quote: a persistent value should always have the same type

Subtopic: database persistence up

Quote: in database programming, data persists after the program; distinguishes database programming languages [»buneP5_1986]

Subtopic: transaction commit up

Quote: a commit instruction is needed for intrinsic persistence; otherwise program failure may lead to an inconsistent database [»buneP5_1986]

Subtopic: temporal database up

Quote: the priority ceiling protocol may be extended to real-time databases with transactions; allows schedule analysis and temporally consistent views [»rajkR_1991]
Quote: a database may retain out-of-date values for items in the database
Quote: a transaction object records a transaction in process; when committed, it becomes a configuration object in the naming structure (history object) [»walpJ6_1988]

Subtopic: time-split b-tree up

Quote: time-split b-tree partitions data into historical data on write-once media and current data; can have copies in both partitions [»lomeD6_1989]
Quote: based time-split b-trees on Easton's write-once b-trees [»lomeD6_1989]
Quote: with time-split b-trees, read-only transactions only need a timestamp for concurrency control; ignores all later records [»lomeD6_1989]

Subtopic: historical values up

Quote: avoid using temporaries for old values of a variable by access to historical values [»takaT8_1980]
Quote: if variable p has a degree 1 history then p<1> is its previous value [»takaT8_1980]
Quote: example of defining Fibonacci numbers with variable history [»takaT8_1980]

Subtopic: immutable data up

Quote: a Cedar rope is an immutable, garbage-collected, text string; widely used in all system levels [»swinDC7_1985]

Subtopic: replicated data up

Quote: replicating persistence uses instructions to move structures in and out of secondary storage; e.g., files, APL [»buneP5_1986]
Quote: concurrent use of replicating persistence requires synchronized extern and intern operations [»buneP5_1986]

Subtopic: const, final, or read-only data up

Quote: a final argument in Java does not prevent changes to the argument's object [»alexRT1_2000]

Subtopic: intrinsic persistence up

Quote: in NIL, variable and file stores are the same [»stroRE5_1985]
Quote: with intrinsic persistence, all values persist as needed; no replicating of data; no distinction between primary and secondary storage [»buneP5_1986]
Quote: a backing store server manages persistent objects with internal names; allocates and frees storage space [»birrAD9_1980]

Subtopic: persistent workspace up

Quote: all-or-nothing persistence saves the state of an interactive session; unstructured, cannot share values, includes volatile structures, depends on programming system [»buneP5_1986]
Quote: APL stores values as arrays; flat, simple data structures

Subtopic: persistent function up

Quote: use persistent functions for program linking [»atkiMP6_1987]
Quote: programs and procedures should be values with a type that may persist [»atkiMP6_1987]

Subtopic: execution log up

Quote: Oberon parameters are typically displayed, and command output is non-volatile with a visible representation; everything is accessible [»wirtN9_1989]

Subtopic: persistent data structure up

Quote: a persistent data structure allows access to any version at any time
Quote: designed a persistent binary search tree with logarithmic operation time and constant space bounds [»drisJR5_1986]
Quote: in persistent data structure, eliminate fat nodes by copying current field values and updating old pointers [»drisJR5_1986]
QuoteRef: simscrip_1971 ;;72 permanent entities in Simscript allocated by Create Each airport with count from attribute n.airport or from subscript on airport which sets n.airport

Subtopic: persistent variable up

Quote: any value should be able to persist; PS-algol was the first practical, persistent language [»buneP5_1986]


Related Topics up

Group: data type   (34 topics, 730 quotes)
Group: data value   (19 topics, 433 quotes)
Group: database   (27 topics, 665 quotes)
Group: variables   (10 topics, 128 quotes)

Topic: archives (19 items)
Topic: frozen representation (6 items)
Topic: configuration management (25 items)
Topic: immutable files and data (59 items)
Topic: input/output by accessing a variable (8 items)
Topic: object-oriented databases (15 items)
Topic: object serialization (13 items)
Topic: read-only and write-once file systems (8 items)
Topic: running programs in a workspace or environment (14 items)
Topic: save-restore (4 items)
Topic: temporal database (25 items)
Topic: temporal relationships (40 items)
Topic: version control (34 items)
Topic: XML data type
(22 items)


Updated barberCB 3/06
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.