Browse Prior Art Database

DYNAMIC DATABASE TABLES

IP.com Disclosure Number: IPCOM000007306D
Original Publication Date: 1994-Oct-01
Included in the Prior Art Database: 2002-Mar-13
Document File: 4 page(s) / 141K

Publishing Venue

Motorola

Related People

Bill Ennis: AUTHOR [+4]

Abstract

A traditional database table may look like: Dynamic Database Tables build off of relational database tables. The extensive use of database links defines a new kind of database table which can adapt when changes need to be made, yet still be able to fallback to an earlier version ifnecessary.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 4

0 M

MOTOROLA Technical Developments Volunie 23 October 1994

DYNAMIC DATABASE TABLES

.

by Bill Ennis, Heather Even, Bob Wong and Jan Warpmski

ABSTRACT: A traditional database table may look like:

  Dynamic Database Tables build off of relational database tables. The extensive use of database links defines a new kind of database table which can adapt when changes need to be made, yet still be able to fallback to an earlier version ifnecessary.

Table 1: 'Ikaditional database table

Person Table

N8OlS

Addlea.

PROBLEMS SOLVED:

  The OMC needs the ability to support databases for objects which have different database schemas. To further explain, an object will have a certain set of entities which define it, but if the software which is running on the object is changed the entities which define it may be different. This means that the same object can have several sets of entities which define it, depending on which sohware version is running on the object at a certain point in time.

Table 1: Traditional database table

Person Table

Age

Occupation

  To further the example, imagine that we need to redefine a person to contain the following information:

  A requirement of the OMC requests a user be able to switch database objects running at an object on command. If we just used a relational database table we would be restricted to using a separate table for each new definition of an object. Each time an object would get re-defined we would have to add a new database table to the database. The OMC needs to be able to switch these without software or database changes in itself.

Table 2: New definition of person

Person Table 2

Addtess

  This invention has eliminated the need for new database tables whenever managed objects are redefined. Supporting multiple database schemas using a new table for each schema would be very hard to maintain and waste a lot of disk space.

Age

Occupation

Spouses Name

INVENTION DESCRIPTION:

  Dynamic Database Tables build off of relational database tables to define a database table at a more complex level. This is done with extensive use of links between rows within a table.

  Now suppose that you have software that needs to support both of these (and possibly others in the future) definitions of a nerson. You have the choice of supporting a separate definition every time it gets

104 0 Motorola, Inc. 1994

[This page contains 15 pictures or other non-text objects]

Page 2 of 4

0 M MO-LA

Technical Developments Volume 23 October 1994

a new definition. We did not want to do this so we it gets converted by a program to its defined type. have re-defined a table in how we use it.

                               We have defined a generic table which we use...