An analysis of geometric modeling in database systems
ACM Computing Surveys (CSUR)
An object-oriented system for engineering applications
SIGMOD '87 Proceedings of the 1987 ACM SIGMOD international conference on Management of data
Semantic data modeling support for CAD
ACM '87 Proceedings of the 1987 Fall Joint Computer Conference on Exploring technology: today and tomorrow
A data model and query language for EXODUS
SIGMOD '88 Proceedings of the 1988 ACM SIGMOD international conference on Management of data
ACM Computing Surveys (CSUR)
Parallelism in processing queries on complex objects
DPDS '88 Proceedings of the first international symposium on Databases in parallel and distributed systems
Performance enhancement through replication in an object-oriented DBMS
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
Gral: an extensible relational database system for geometric applications
VLDB '89 Proceedings of the 15th international conference on Very large data bases
An object-oriented data model for partition processing in distributed databases
SIGSMALL '90 Proceedings of the 1990 ACM SIGSMALL/PC symposium on Small systems
An extensible kernel object management system
OOPSLA '91 Conference proceedings on Object-oriented programming systems, languages, and applications
An object-oriented data model for partition processing in distributed databases
ACM SIGSMALL/PC Notes
Rule-based optimization and query processing in an extensible geometric database system
ACM Transactions on Database Systems (TODS)
Working with Persistent Objects: To Swizzle or Not to Swizzle
IEEE Transactions on Software Engineering
Supporting general queries in an object management system
SAC '92 Proceedings of the 1992 ACM/SIGAPP Symposium on Applied computing: technological challenges of the 1990's
Information resource management: integrating the pieces
ACM SIGMIS Database
Linking object oriented database and hypertext to support software documentation
SIGDOC '92 Proceedings of the 10th annual international conference on Systems documentation
Persistent Caching: An Implementation Technique for Complex Objects with Object Identity
IEEE Transactions on Software Engineering
Toward the semantic geospatial web
Proceedings of the 10th ACM international symposium on Advances in geographic information systems
The ROSE Data Manager: Using Object Technology to Support Interactive Engineering Applications
IEEE Transactions on Knowledge and Data Engineering
MORE: An Object-Oriented Data Model with a Facility for Changing Object Structures
IEEE Transactions on Knowledge and Data Engineering
Object-Oriented Query Languages: The Notion and the Issues
IEEE Transactions on Knowledge and Data Engineering
Conceptual Database Evolution Through Learning in Object Databases
IEEE Transactions on Knowledge and Data Engineering
VLDB '90 Proceedings of the 16th International Conference on Very Large Data Bases
A Framework for Automating Physical Database Design
VLDB '91 Proceedings of the 17th International Conference on Very Large Data Bases
Data management in environmental information systems
Handbook of massive data sets
International Journal of Computer Applications in Technology
| Hi-index | 0.00 |
A database system is a collection of stored data together with their description (the database) and a hardware/software system for their reliable and secure management, modification and retrieval (the database management system, DBMS).A database is supposed to represent the interesting semantics of an application (the miniworld) as completely and accurately as possible. The data model incorporated into a database system defines a framework of concepts that can be used to express the miniworld semantics.It comprisesbasic data types and constructors for composed data types,(generic) operators to insert, manipulate, retrieve and delete instances of the actual data types of a database,implicit consistency constraints as well as (eventually) mechanisms for the definition of explicit consistency constraints that further reflect the miniworld semantics as viewed by the database system.As usual, types have to be defined before instances of them can be created (the collection of defined types — sometimes together with the set of explicit consistency constraints — forms the database schema). Every database thus adheres to the schema defined for it, and both together, the schema and the actual data provided by the users (and stored in instances) capture the miniworld semantics.We can therefore distinguish the following two classes of semantics:the semantics of the miniworld itself,the semantics of the miniworld as represented within the database. Let us assume that a database correctly reflects the intended miniworld semantics (careful database design!). Due to the rigid framework of data models, there will still remain a semantic gap between the miniworld and its database representation. In other words, it is usually impossible to represent all interesting semantics within a database. The “remainder” has to be captured by the application programs using the database and/or it is part of the (hopefully meaningful!) interpretation of the result of database queries by the user himself.However, the ultimate goal of database systems is to provide for concepts that allow to keep the semantic gap as small as possible and thus permit to represent most of the salient semantics in the database itself.