Results 1 - 10
of
24
A Transaction Model for Active Distributed Object Systems
, 1992
"... data types are programming language constructs that encapsulate the representations of a set of objects and a set of operations on these objects. The operations are the only means of accessing and manipulating the objects. From the perspective of transaction processing, ADTs introduce a need to deal ..."
Abstract
-
Cited by 55 (4 self)
- Add to MetaCart
data types are programming language constructs that encapsulate the representations of a set of objects and a set of operations on these objects. The operations are the only means of accessing and manipulating the objects. From the perspective of transaction processing, ADTs introduce a need to deal with abstract operations. The operations of transactions that execute on ADTs are not simple reads and writes, but are more abstract, such 5.2 Transaction Schemes 13 Transaction Structure simple objects instances of ADTs complex objects flat transactions closed nesting open nesting combinations active objects [DAYA88] [STON90] [BADR88] [WEIH88] [HERL90] [ESWA75] [BERN87] [MOSS85] [GARC87] [GARC90] DOM [ELMA90] [PU88] [FEKE89] [BANC85] [KOTZ88] [FARR89] Object Structure FIGURE 5.2 Representation of transaction model space and examples. The labels for the references are given following each citation in the Bibliography. 14 Chapter 5. Transaction Model for Distributed Object Systems as Ins...
Dynamic Restructuring of Transactions
"... Open-ended activities are characterized by uncertain duration, unpredictable developments, and interactions with other concurrent activities. Like other database applications, they require consistent concurrent access and fault-tolerance, but their unconventional characteristics are incompatible wit ..."
Abstract
-
Cited by 36 (5 self)
- Add to MetaCart
(Show Context)
Open-ended activities are characterized by uncertain duration, unpredictable developments, and interactions with other concurrent activities. Like other database applications, they require consistent concurrent access and fault-tolerance, but their unconventional characteristics are incompatible with the conventional database mechanisms of concurrency and failure atomicity. We present the split-transaction and join-transaction operations for restructuring in-progress transactions, as an approach to consistent concurrent access and fault-tolerance for open-ended activities. Split-transaction divides an on-going transaction into two or more transactions that are serializable with respect to each other and all other transactions, and each of the new transactions is later committed or aborted independently of the others. Jointransaction merges two or more transactions that are serializable with respect to each other into a single transaction as if they had always been part of the same tra...
Principles of Object-Oriented Query Languages
- Proc. GI Conf. on Database Systems for Office, Engineering, and Scientific Applications
, 1991
"... We survey the fundamental problems of designing general purpose, descriptive query languages for object-oriented database systems. Structural aspects of object models are investigated and their implications on the query language capabilities are analyzed and summarized as requirements that should be ..."
Abstract
-
Cited by 19 (6 self)
- Add to MetaCart
We survey the fundamental problems of designing general purpose, descriptive query languages for object-oriented database systems. Structural aspects of object models are investigated and their implications on the query language capabilities are analyzed and summarized as requirements that should be met by a `good' object-oriented query language. The type system of an OODB model has to distinguish atomic types (such as basic data types -- numbers, strings, -- or abstract object types) and constructed types (such as sets and tuples). Each of the type constructors should be supported by an adequate set of generic access and manipulation operators. The query language should allow orthogonal combination of operators according to the nesting structure of type constructors, the model should be closed against its operators, and the language should be adequate. The latter criterion ensures, for instance, that queries can be expressed that return objects instead of just data about objects ("object preservation"). Several recent proposals for query languages are evaluated against these criteria.
Empirical modelling and the foundations of artificial intelligence
- In Proceedings of International Workshop on Computation for Metaphors, Analogy and Lecture Notes in Artificial Intelligence 1562
, 1999
"... Abstract. This paper proposes Empirical Modelling (EM) as a possi-ble foundation for AI research outside the logicist framework. EM offers principles for constructing physical models, typically computer-based, by construing experience in terms of three fundamental concepts: ob-servables, dependency ..."
Abstract
-
Cited by 6 (0 self)
- Add to MetaCart
(Show Context)
Abstract. This paper proposes Empirical Modelling (EM) as a possi-ble foundation for AI research outside the logicist framework. EM offers principles for constructing physical models, typically computer-based, by construing experience in terms of three fundamental concepts: ob-servables, dependency and agency. EM is discussed in the context of critiques of logicism drawn from a variety of sources, with particular reference to the five foundational issues raised by Kirsh in his paper
Evolution towards, in, and beyond Object Databases
, 1994
"... . There is a manifold of meanings we could associate with the term "evolution" in the database arena. This paper tries to categorize some of these into a unique framework, showing similarities and differences. Among the topics touched upon are: extending traditional data models to become & ..."
Abstract
-
Cited by 4 (1 self)
- Add to MetaCart
. There is a manifold of meanings we could associate with the term "evolution" in the database arena. This paper tries to categorize some of these into a unique framework, showing similarities and differences. Among the topics touched upon are: extending traditional data models to become "object-oriented", migrating existing data to (not necessarily OO) databases, schema extension and modification in a populated database, integration of federated systems, and the use of "external services" to enrich DBMS functionalities. The following are presented in more detail: first, we describe the necessity of object evolution over time; second, we discuss schema evolution; and third, we present evolutionary database interoperability by identifying different coupling levels. A few basic mechanisms, such as views (derived information) and a uniform treatment of data and meta data, and type and/or class hierarchies, allow for a formal description of (most of) the relevant problems. Beyond presentin...
Maintaining Semantics In The Integration Of Network Interoperable Product Data Models
, 1997
"... ..."
Extensions to the Relational Data Model
- Conceptual Modelling, Databases and CASE: An Integrated View of Information Systems Development. Jon
, 1992
"... this paper we give an overview of research on extensions of relational database technology. In order to systematically classify different ways to extend the data model we take a programming language point of view of data models: a data model consists of a set of basic (predefined) types, a set of ty ..."
Abstract
-
Cited by 2 (1 self)
- Add to MetaCart
(Show Context)
this paper we give an overview of research on extensions of relational database technology. In order to systematically classify different ways to extend the data model we take a programming language point of view of data models: a data model consists of a set of basic (predefined) types, a set of type constructors (or structuring primitives), and a set of operators (for the predefined as well as constructed types). Extensions to each of of these data model constituents are possible and have indeed been investigated in the past. Our presentation focuses on extensions to the type system (primitives and constructors) and those extensions to the operators that are implied by them. During the 1980's, there has been a significant trend in database research addressing the problem of supporting non-traditional database applications. Though relational database systems (RDBMSs) entered the commercial marketplace in the early eighties, it seemed clear that, at least without major enhancements, they would not be appropriate for non-business applications. Several research groups started out to either enhance RDBMS technology in several ways or to develop completely different models and systems. Throughout this paper we limit our scope to those investigations that tried to keep some of the characteristics of the relational model and/or systems. Attempts to make semantic data models operational, for instance, Entity-Relationship models, have already been discussed in this volume before. Also, extensions in query languages' expressive power to deal with recursion, will be surveyed in a subsequent series of articles, as will the object-oriented approaches. Therefore, we will take a more "conservative" approach, that is, stay closer within the original relational framework. The relationa...
Evolution of Relational Database to Object-Relational Database in Abstract Level
- Proceedings of the International Workshop on Principles of Software Evolution
, 1999
"... Level Pujianto Yugopuspito 1;2 andKeijiroAraki 1 1 Department of Computer Science and Communication Engineering Graduate School of Information and Electrical Engineering Kyushu University, 6-1 Kasuga Koen, Fukuoka 816-8580, JAPAN E-mail: #pyugop, araki#@dontaku.csce.kyushu-u.ac.jp 2 PT. ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
(Show Context)
Level Pujianto Yugopuspito 1;2 andKeijiroAraki 1 1 Department of Computer Science and Communication Engineering Graduate School of Information and Electrical Engineering Kyushu University, 6-1 Kasuga Koen, Fukuoka 816-8580, JAPAN E-mail: #pyugop, araki#@dontaku.csce.kyushu-u.ac.jp 2 PT. IPTN, Indonesian Aircraft Manufacture, Inc. Jl. Pajajaran 154, Bandung 40174, Indonesia ABSTRACT Relational Database is a mature database with a rigorous speci#cation and is broadly applicable. The de#- cient in data representation has been known since the software application changed to object oriented. An effort should be taken to encounter the connection between existing Relational Database with a new software application that is object oriented. In a case where a complete migration is not the choice of solution since the existing Relational Database should be preserved, then an Object-Relational Database might be a solution. The evolution of Relational Database to ObjectRelational Dat...
Database Trends and Directions: Current Challenges nd Opportunities
"... Abstract. Database management has undergone more than four decades of evolution producing vast range of research and extensive array of technology solutions. The database research community and software industry has responded to numerous challenges resulting from changes in user requirements and opp ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Abstract. Database management has undergone more than four decades of evolution producing vast range of research and extensive array of technology solutions. The database research community and software industry has responded to numerous challenges resulting from changes in user requirements and opportunities presented by hardware advances. The relational database approach as represented by SQL databases has been particularly successful and one of the most durable paradigms in computing. Most recent database challenges include internet-scale databases – databases that manage hundreds of millions of users and cloud databases that use novel techniques for managing massive amounts of data. In this paper we review the evolution of database management systems over the last four decades and then focus on the most recent database developments discussing research and implementation challenges presented by modern database applications.
