View in EDS

Persistence in the Object-Oriented Database Programming Language VML

Saved in:
Bibliographic Details
Title: Persistence in the Object-Oriented Database Programming Language VML
Authors: Volker Turau, Wolfgang Klas
Contributors: The Pennsylvania State University CiteSeerX Archives
Source: ftp://ftp.darmstadt.gmd.de/pub/oasys/reports/P-93-19.ps.Z
Publication Year: 1992
Collection: CiteSeerX
Subject Terms: persistency, object-oriented programming, object-oriented modelling, database systems, database programming languages
Description: In this paper the principles of handling persistent objects in the object-oriented database programming language VML are presented. The main design criteria of VML with respect to persistence were: persistence independent programming, data type completeness and operations manipulating the extension of a class. After defining the above mentioned concepts an example is used to compare the modelling and computational power of VML with the database programming languages Adaplex, PS-algol, and Galileo. The distinction of types and classes is the basis for defining persistence in VML. Instances of classes are always persistent and those of data types are always transient. All instances are referenced by object identifiers, values of datatypes are referenced independently of the fact whether they are attached to persistent objects (and are therefore persistent itself) or whether they are "stand alone". Keywords: persistency, object-oriented programming, object-oriented modelling, database sys.
Document Type: text
File Description: application/postscript
Language: English
Relation: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.55.8214
Availability: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.55.8214
Rights: Metadata may be used without restrictions as long as the oai identifier remains attached to it.
Accession Number: edsbas.F43C643D
Database: BASE
Description
Abstract:In this paper the principles of handling persistent objects in the object-oriented database programming language VML are presented. The main design criteria of VML with respect to persistence were: persistence independent programming, data type completeness and operations manipulating the extension of a class. After defining the above mentioned concepts an example is used to compare the modelling and computational power of VML with the database programming languages Adaplex, PS-algol, and Galileo. The distinction of types and classes is the basis for defining persistence in VML. Instances of classes are always persistent and those of data types are always transient. All instances are referenced by object identifiers, values of datatypes are referenced independently of the fact whether they are attached to persistent objects (and are therefore persistent itself) or whether they are "stand alone". Keywords: persistency, object-oriented programming, object-oriented modelling, database sys.