Object versioning

Details Object versioning Object versioning

2007-04-24

2007-04-24

Mofiz, Apu (Department: 2165)

Data processing: database and file management or data structures

Database design

Data structure types

C707S793000

Reexamination Certificate

active

10735217

ABSTRACT:
A repository contains multiple versions of an object, and any version of the object can be modified by a user, as and when necessary. A table for one object (“first object”) that is contained in another object (“second object”) has at least two columns, namely one column for a minimum version of the second object and another column for a maximum version of the second object. If a number of versions of the first object are responsive to a query, then one version of the first object is selected if a version of the second object that is responsive to the query happens to be in the range defined by the just-described minimum version number and the maximum version number. Depending on the embodiment, the second object can be an immediate parent of the first object, or can be an ancestor (also called “first class object”) of the first object that is not contained in any other object. In some embodiments, one or more attributes of the first object are stored in a first table along with a unique identifier and a version number. In addition, information on relations of the first object to other objects as well as an identity of a configuration (to which the current version of the first object belongs) are stored in a second table. Therefore, a pair of tables are used for each object, so as to decouple information that defines an object from information on relationships of the object. If a change happens in just the relationship of an object then no change is made to the table containing the definition of the object. Similarly, if a change happens in just the definition of the object, then no change is made to the table containing the relations of the object. Moreover, when a change happens to an object, if the object has a number of ancestors and decendants only an immediate parent of the object is updated, thereby to eliminate a versioning chain reaction (i.e. other objects are not affected).

REFERENCES:
patent: 5181162 (1993-01-01), Smith et al.
patent: 6347388 (2002-02-01), Hollander
patent: 6460052 (2002-10-01), Thomas et al.
S. Ducasse et al., “A Reflective Model for First Class Dependencies”, published in Proceedings of ACM OOPSLA'95, pp. 265-280, 1995.
S. Ducasse, “Inheritance Mechanism Reification by Means of First Class Object”, published in Proceedings of the IJCA'95 workshop on Reflection and MetaLevel Architectures and their Applications in AI, pp. 39-49, 1995.

Affiliated with

Also associated with

Rating

Object versioning does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Object versioning, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Object versioning will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3790172