Browse Prior Art Database

Generic Database Interface

IP.com Disclosure Number: IPCOM000103326D
Original Publication Date: 1990-Oct-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 45K

Publishing Venue

IBM

Related People

Blakely-Fogel, D: AUTHOR [+2]

Abstract

A low-maintainence method for use of database management interfaces is described. This method results in an interface layer between the database manager and the application that can be easily updated if the database management interface changes. This interface layer can also be shared by many different applications.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 84% of the total text.

Generic Database Interface

      A low-maintainence method for use of database management
interfaces is described.  This method results in an interface layer
between the database manager and the application that can be easily
updated if the database management interface changes.  This interface
layer can also be shared by many different applications.

      The responsibility of this interface is threefold.  It must
convert the application's data to a format acceptable to the database
manager and it must convert the database manager's data to a format
acceptable to the application. This can be done by using a table of
knowledge-based rules that describe the characteristics of the data
to be stored and manipulated by the data manager.  This table
contains information such as how the data is stored in the database
(i.e. integer, short, character, ...) and how the application expects
the data to be returned.  It also contains enough information to
determine where the data should be put for both the database manager
and the application.  In short, it contains all rules necessary to
convert the data from the application's format to the database
manager's format.  It also contains all rules necessary to convert
the data from the database manager's format to the application's
format.  Its third responsibility is to make the necessary interface
calls to the database manager and interpret the results for the
application

      By using this method, the database m...