Emc Corporation

Open Text Corporation

Yik-Ping Li

Victor Spivak

Shu-Shang Sam Wei

Meir Amiel

Roger W Kilday

Venkat Chandrasekaran

Xiaofeng Ma

David Buccola

Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type is shared by one or more other instances of the lightweight type.

System for lightweight objects

Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type is shareable by one or more other instances of the lightweight type.

Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. One or more instances of the lightweight type share the instance of the sharable type.

Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type may be shared by one or more other instances of the lightweight type.

Processing an object that shares a parent with another object is disclosed. An indication is received with respect to an object that shares a parent object instance with one or more other objects that a change associated with the object is to be made to a data comprising the shared parent object instance. The parent object instance is cloned to create a new parent object instance. The new parent object instance is designated as the parent of the object instance.

Conversion of lightweight object to a heavyweight object

Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes includes a plurality of attribute values associated with an object and is stored in a single database field that is not specific to any one attribute in the combined set of attributes.

Efficient storage of non-searchable attributes

Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Retrieval of searchable and non-searchable attributes

An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level.

Optimized fetching for customization object attributes

Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

An attribute is received for storage. Whether the attribute is searchable or non-searchable in storage is determined. Storing the attribute as a searchable attribute comprises storing the attribute in a database table corresponding to a hierarchical class-based object. Storing the attribute as a non-searchable attribute comprises storing the attribute together with one or more other non-searchable attributes as a set of attributes. The set of attributes is stored in a database location outside the database table corresponding to the hierarchical class-based object, and the database location is accessed before the database table. A unique attribute identifier is associated with the attribute to distinguish between a name of the attribute and a name of one of the one or more other non-searchable attributes in the event that the name of the attribute and the name of the one of the one or more other non-searchable attributes are assigned the same name.

Identifiers for non-searchable attributes

Managing stored content is disclosed. It is determined that a new or modified attribute is to be associated with future-created instances of an object type but not with at least some previously-created instances of the object type. A default intra-type customization that associates the new or modified attribute with future-created instances of the object type, in a manner that results in the new or modified attribute being stored in a database structure that is separate from a type-specific structure configured to store one or more type-based attributes common to both the at least some previously-created and future-created instances of the object type, is associated with the object type.

Growing community of inventors

Fremont, CA, United States of America

Yik-Ping Li