Browse Prior Art Database

Generic Dynamic SQL Application Programming Interface Set

IP.com Disclosure Number: IPCOM000105650D
Original Publication Date: 1993-Aug-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 6 page(s) / 214K

Publishing Venue

IBM

Related People

Hidalgo, DS: AUTHOR

Abstract

Disclosed is an invention which provides a set of generic dynamic SQL Application Programming Interfaces (APIs) that allows the support of dynamic SQL for application programs without being statically tied to a specific Relational Database Management System (RDBMS). The use of embedded SQL by a database application to support dynamic SQL causes the application to be statically tied to the RDBMS to which it is precompiled, compiled and linked. It also forces all of the RDBMS's restrictions on the database application. Relating the application to a different RDBMS requires the application to be rebuilt.

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

Generic Dynamic SQL Application Programming Interface Set

      Disclosed is an invention which provides a set of generic
dynamic SQL Application Programming Interfaces (APIs) that allows the
support of dynamic SQL for application programs without being
statically tied to a specific Relational Database Management System
(RDBMS).  The use of embedded SQL by a database application to
support dynamic SQL causes the application to be statically tied to
the RDBMS to which it is precompiled, compiled and linked.  It also
forces all of the RDBMS's restrictions on the database application.
Relating the application to a different RDBMS requires the
application to be rebuilt.  A generic interface that can be used by
an application in place of embedded SQL would isolate the application
program from the mechanisms used by the interface to communicate with
multiple RDBMS's and it can also allow RDBMS's restrictions to be
transparently circumvented when necessary.

      The specific features of this generic dynamic SQL API set are
described in the paragraphs that follow:

o   RDBMS independence.  An application program linked to the
    disclosed API set can offer its users the relational database
    function without dependence on the specific RDBMS used to support
    it.

o   RDBMS access scheme independence.  The application program linked
    to this API set has no dependency on the method or scheme used by
    these APIs to access the RDBMS.  Potential schemes include a
    socket-based Client/Server, an Remote Procedure Call (RPC)-based
    Client/Server or a local DBM server accessed through Inter
    Process Communication, etc.

o   Multiple concurrent database connections per application process.
    The abstraction of a database connection as a handle gives the
    application program the capability to concurrently establish and
    manage multiple database connections, even if the underlying
    RDBMS doesn't directly support this capability.

o   Dynamic SQL support without embedded SQL.  The application
    program using this API set can obtain dynamic SQL support without
    the need for precompilation and binding.  Database application
    programs that only need to support dynamic SQL normally use
    embedded SQL statements to prepare and/or execute the dynamic
    SQL, to open and close cursors, to fetch rows of data, and to
    commit or rollback their transactions.  The embedded SQL
    statements must then be converted to host language by using a
    precompiler on the embedded SQL program module.  Since the
    precompiler generated code references RDBMS product specific
    runtime API functions, making the application program apply the
    dynamic SQL against a different RDBMS product requires
    re-precompiling, re-compiling and re-linking the application
    program.  In other words, the use of embedded SQL directly by the
   ...