Advertisement

The object shell: An extensible system to define an object-oriented view of an existing database

  • Rafiul Ahad
Integration Of Existing Systems
Part of the Lecture Notes in Computer Science book series (LNCS, volume 334)

Abstract

The design of an extensible system, called the object shell, to define and query an object-oriented view of an existing database is described. An object-oriented view is defined by identifying the object types and the functions between them that are present in the existing database. The object shell provides facilities to declaratively define the logical schema, implementation methods for functions, the cost associated with the implementation methods, and the query optimization knowledge. An implementation method is a sequence of access routine calls. Access routines are defined by the database administrator (DBA), and each of them encodes the detailed knowledge to access a single physical structure (e.g., a file). The query interface of the object shell allows the user to issue queries against the view. The object shell translates the user query into an efficient program that calls the access routines to retrieve the required data.

Keywords

Output Port Transformation Rule Input Port Function Node Access Structure 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

7. References

  1. [Ahad85]
    Ahad, R., Baparao, K., McLeod, D., “On Estimating the Cardinality of the Projection of a Database Relation”, to appear in ACM Transactions on Database Systems.Google Scholar
  2. [Ahad86]
    Ahad, R. and McLeod, D., “Performance Optimization Techniques for an Object-Oriented Semantic Data Model”, CRI Technical Report, USC, 1986.Google Scholar
  3. [Bato86]
    Batory, D.S. et al., “GENESIS: A Reconfigurable Database Management System”, TR 86-07, Dept. of Computer Sciences, The University of Texas, Austin, 1986.Google Scholar
  4. [Bune79]
    Buneman, P. and Frankel, R. “FQL-A Functional Query Language”, Proc. ACM-SIGMOD Conference, May, 1979.Google Scholar
  5. [Care86]
    Carey, M. et al., “The architecture of EXODUS Extensible DBMS”, Proc. of the Int. Workshop on Object-Oriented Database Systems, Asilomar, California, September, 1986.Google Scholar
  6. [Cloc86]
    Clocksin, W. F. and C. S. Mellish, Programming in Prolog, Springer Verlag, 1986.Google Scholar
  7. [Codd70]
    Codd, E.F., “A Relational Model of Data for Large Shared Data Banks”, CACM, 13(6), June 1970.Google Scholar
  8. [Daya84]
    Dayal, U. and Hwang, H, “View Definition and Generalization for Database Integration in a Multidatabase System”, IEEE Transactions on Software Engineering, Vol SE-10, November, 1984Google Scholar
  9. [Daya85]
    Daya, U. and Smith, J., “PROBE: A Knowledge Oriented Database Management System, Proc. of the Islamorada Workshop on Large Scale Knowledge Base and Reasoning Systems, February, 1985.Google Scholar
  10. [Fish87]
    Fishman, D., et al., “Iris: An Object-Oriented Database Management System”, ACM Transactions on Office Information Systems, Vol 5, No. 1, January 1987.Google Scholar
  11. [Frey86]
    Freytag, J.C., and Goodman, N, “Rule-Based Transformation of Relational Queries into Iterative Programs”, Proc. ACM-SIGMOD Conference, Washington, D.C., May, 1986.Google Scholar
  12. [Frey87]
    Freytag, J.C., “A Rule-Based View of Query Optimization”, Proc. ACM SIGMOD Conference, San Francisco, May, 1987.Google Scholar
  13. [Grae87]
    Graefe, G. and DeWitt, D., “The EXODUS Optimizer Generator”, Proc. ACM SIGMOD Conference San Francisco, May 1987.Google Scholar
  14. [Kent79]
    Kent, W., “Limitations of Record-Based Information Models”, ACM Transactions on Database Systems, 4(1), March, 1979.Google Scholar
  15. [King86]
    King, R., “A database Management System Based on an Object-Oriented Model”, Proceedings of the First International Workshop on Expert Database Systems, Kiawah Island, 1986.Google Scholar
  16. [Motr81]
    Motro, A. and Buneman, P., “Constructing Superviews”, Proc. SIGMOD 1981.Google Scholar
  17. [Motr87]
    Motro, A., “Superviews: Virtual Integration of Multiple Databases”, IEEE Transactions on Software Engineering, Vol SE-13, No. 7, July 1987.Google Scholar
  18. [Rose87]
    Rosenthal, A. and Helman, P., “Understanding and Extending Transformation-Based Optimizers”, Database Engineering 1987.Google Scholar
  19. [Schw86]
    Schwarz, P. et. al., “Extensibility in the Starbust Database System”, Proc. of the Asilomar Workshop on Object-Oriented Database Systems, September, 1986.Google Scholar
  20. [Ship81]
    Shipman, D.W., “The Functional Data Model and the Data Language DAPLEX”, ACM Transactions on Database Systems, 6(1), March,1981.Google Scholar
  21. [Ston86]
    Stonebraker, M. and Rowe, L., “The Design of Postgres”, Proc. ACM SIGMOD Conference, Washington, 1986.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1988

Authors and Affiliations

  • Rafiul Ahad
    • 1
  1. 1.Information Systems Group College of Business and ManagementUniversity of MarylandCollege ParkMaryland

Personalised recommendations