Method and system for multi-entry and multi-template...

Details Method and system for multi-entry and multi-template... Method and system for multi-entry and multi-template...

1998-03-20

2001-01-30

Alam, Hosain T. (Department: 2771)

Data processing: database and file management or data structures

Database design

Data structure types

C707S793000

Reexamination Certificate

active

06182083

ABSTRACT:

The following identified U.S. patent applications are relied upon and are incorporated by reference in this application.
Provisional U.S. Patent Application No. 60/076,048, entitled “Distributed Computing System,” filed on Feb. 26, 1998.
U.S. patent application Ser. No. 09/044,923, entitled “Method and System for Leasing Storage,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,838, entitled “Method, Apparatus, and Product for Leasing of Delegation Certificates in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,834, entitled “Method, Apparatus and Product for Leasing of Group Membership in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,916, entitled “Leasing for Failure Detection,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,933, entitled “Method for Transporting Behavior in Event Based System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,919, entitled “Deferred Reconstruction of Objects and Remote Loading for Event Notification in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,938, entitled “Methods and Apparatus for Remote Method Invocation,” filed on the same date herewith.
U.S. patent application Ser. No. 09/045,652, entitled “Method and System for Deterministic Hashes to Identify Remote Methods,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,790, entitled “Method and Apparatus for Determining Status of Remote Objects in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,930, entitled “Downloadable Smart Proxies for Performing Processing Associated with a Remote Procedure Call in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,917, entitled “Suspension and Continuation of Remote Methods,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,839, entitled “Method and System for In-Place Modifications in a Database,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,945, entitled “Method and System for Typesafe Attribute Matching in a Database,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,931, entitled “Dynamic Lookup Service in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,939, entitled “Apparatus and Method for Providing Downloadable Code for Use in Communicating with a Device in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,826, entitled “Method and System for Facilitating Access to a Lookup Service,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,932, entitled “Apparatus and Method for Dynamically Verifying Information in a Distributed System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/030,840, entitled “Method and Apparatus for Dynamic Distributed Computing Over a Network,” and filed on Feb. 26, 1998.
U.S. patent application Ser. No. 09/044,938, entitled “An Interactive Design Tool for Persistent Shared Memory Spaces,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,934, entitled “Polymorphic Token-Based Control,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,915, entitled “Stack-Based Access Control,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,944, entitled “Stack-Based Security Requirements,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,837, entitled “Per-Method Designation of Security Requirements,” filed on the same date herewith.
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates to database systems and, more particularly, to entry storage in database systems. The invention also relates to query matching methodologies employed in database systems.
2. Description of the Related Art
Database systems are serving increasingly important roles in today's society. The amount of data that may be stored by typical database systems is growing at staggering rates, and providing expedient and flexible access to the data is often vital. However, the job of designing database systems which perform in an optimal manner is difficult.
A particularly important consideration in database design is to store the data so that it can be used for a wide variety of applications and such that the manner in which it may be used can be changed quickly and easily. It is further often desirable to allow additional data types or categories to be added without significantly affecting other portions of the database system.
Unfortunately, it is remarkably difficult to change the way data is used and organized in many database systems, and to allow for additional data types and categories. Modifications can set off a chain reaction of changes to programs and other components of the database system, and hence can be exceedingly expensive to accomplish. Consequently, data processing has tended to become frozen into its old data structures. Additionally, designers of database systems tend to make numerous intricate trade-offs between one aspect of the design and another, thus leading to a less than optimal resulting design.
To elaborate further, storing information in a database system is usually done by exact type; that is, a record stored in a database system typically has a certain number and type of fields, such as a tuple in a relation of a relational database. Each field may be defined to store a particular type of data, such as string data, integer data, boolean data, or some other data type, as desired. If a user wants to look-up information in the database, the user must look-up the exact record type (i.e., records of different types are typically searched independently). Thus, if data in which the searcher is interested may be in a record of any one of several different types, the searcher must know in advance which record types might exist, or have some explicit way of asking for all types. The searcher is then required to explicitly look through all possible record types to find the particular record of interest. This complicates the software associated with the search engine and can practically limit the number of different record types that can be maintained.
Furthermore, fields in a record in a database typically do not refer to other records. This reduces the amount and kind of information a single record typically holds. Consequently, databases are limited by their inability to store and manipulate records that are sets of records.
In addition, a record in a typical database is usually not associated with characteristics apart from the actual data itself. For example, when data is found, there is no way to associate behavior with the record that changes with the record type, thus allowing the program to use various records returned by the match in a single way to achieve record-type specific results.
Regarding another aspect of database systems, the usual way of specifying attributes or properties in a database is by a simple set of <name, value> pairs, where the values are either restricted to strings or else are of arbitrary type (type “any”). There is no way to restrict type in these <name, value> pairs, and hence, there is no enforcement that a particular name must always have a value of a particular type. For example, in a hypothetical printer, the “speed” attribute, representing how many pages-per-minute the printer can print, should be enforced as an integer to ensure a user does not set it to something else, such as “about 10 ppm” or “8 to 10.” The same kind of problem exists if the values can be objects of any type. In that case, a user can set the attribute to an integer object instead of a string object but still cannot prevent another user from incorrectly storing a string object in an attribute that should only be set to integers.
Furthermore, previous systems

Affiliated with

Also associated with

Rating

Method and system for multi-entry and multi-template... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method and system for multi-entry and multi-template..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for multi-entry and multi-template... will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2492658