Intermedia: A case study of the differences between relational and object-oriented database systems
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
Concurrency control in advanced database applications
ACM Computing Surveys (CSUR)
The ObjectStore database system
Communications of the ACM
The POSTGRES next generation database management system
Communications of the ACM
The human genome project and informatics
Communications of the ACM
Working with Persistent Objects: To Swizzle or Not to Swizzle
IEEE Transactions on Software Engineering
Persistence software: bridging object-oriented programming and relational databases
SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
The object database standard: ODMG 2.0
The object database standard: ODMG 2.0
Client Data Caching: A Foundation for High Performance Object Database Systems
Client Data Caching: A Foundation for High Performance Object Database Systems
Building a Laboratory Information System Around a C++-Based Object-Oriented DBMS
VLDB '94 Proceedings of the 20th International Conference on Very Large Data Bases
Computational Proxies: Modeling Scientific Applications in Object Databases
Proceedings of the Seventh International Working Conference on Scientific and Statistical Database Management
The Design and Implementation of a Database For Human Genome Research (Position Paper)
SSDBM '96 Proceedings of the Eighth International Conference on Scientific and Statistical Database Management
Constructing a Domain-Specific DBMS using a Persistent Object System
Proceedings of the Sixth International Workshop on Persistent Object Systems
| Hi-index | 0.00 |
The growing maturity of ODBMS technology is causing many enterprises to consider migrating relational databases to ODBMS's. While data remapping is relatively straightforward in most cases, greater challenges lie in economically and non-invasively adapting legacy application software. We report on a genetics laboratory database migration experiment, which was facilitated by both organization of the relational data in object-like form and a C++ framework designed to insulate application code from relational artifacts. Although this experiment was largely successful, we discovered to our surprise that the framework failed to encapsulate three subtle aspects of the relational implementation, thereby "contaminating" application code. We analyze the underlying issues, and offer cautionary guidance to future migrators.