SYSTEMS AND METHODS FOR IMPLEMENTING MANY OBJECT TO OBJECT RELATIONSHIPS IN A MULTI-TENANT ENVIRONMENT

• US 20080162544A1
• Filed: 12/27/2006
• Published: 07/03/2008
• Est. Priority Date: 12/27/2006
• Status: Abandoned Application

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Weissman, Craig, Wong, Simon, Tamm, Steven
• Application Number:
  US11/616,744
• Publication Number:
  US 20080162544A1
• Time in Patent Office: Days
• US Class Current: 707/103R
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/2228 Indexing structures

Abstract

Systems and methods for storing relationship information for an information object in a database system. Methods and mechanisms for storing relationship information for information objects enable database systems to store and retrieve data objects having an arbitrary number of relationships with one another. This ability to store and retrieve data objects by relationship(s) enables more efficient searching of database objects and removal of constraints on the number of relationships that would otherwise exist when objects are stored in a database.

Claims

1. A method of storing relationship information for an information object in a database system, comprising:

receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database, the plurality of portions comprising a single table of the database (“

main table”

), the information object relating to at least one other information object by relationship information identifying the other information object in the database; and

storing the relationship information to an index table (“

index table”

) enabling locating information objects related to the information object received without searching the main table, once the information object is stored in the main table.

2. The method of claim 1, wherein receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database includes:

receiving a user defined (custom) object having at least one relationship to at least one other object, the at least one other object comprising at least one of another custom object and a predefined (standard) object.

3. The method of claim 1, wherein receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database includes:

receiving a pre-defined (standard) object having at least one relationship to at least one other object indicated by at least one user defined (custom) field, the at least one other object comprising at least one of a user defined (custom) object and another predefined (standard) object.

4. The method of claim 1, wherein storing the relationship information to an index table includes:

storing relationship information in a multi-way uniquely indexed table.

5. The method of claim 4, wherein storing relationship information in a multi-way uniquely indexed table includes:

storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction using the same index table.

6. The method of claim 5, wherein storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction using the same index table includes:

storing relationship information in the index table based on the organization id, relationship id and source entity id, and also by organization id, relationship id, and target entity id.

7. The method of claim 4, wherein storing relationship information in a multi-way uniquely indexed table includes:

storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction regardless of the original source table.

8. The method of claim 1, wherein storing the relationship information to an index table includes:

storing a target entity id with a set of custom fields in the main table and in the index table.

9. The method of claim 8, wherein storing a target entity id with a set of custom fields in the main table and in the index table enables:

applying relationships to standard objects.

10. A machine-readable medium carrying one or more sequences of instructions for storing relationship information for an information object in a database system, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database, the plurality of portions comprising a single table of the database (“

main table”

), the information object relating to at least one other information object by relationship information identifying the other information object in the database; and

storing the relationship information to an index table (“

index table”

) enabling locating information objects related to the information object received without searching the main table, once the information object is stored in the main table.

11. The machine-readable medium as recited in claim 10, wherein the instructions for carrying out the step of receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database include instructions for carrying out the step of:

receiving a user defined (custom) object having at least one relationship to at least one other object, the at least one other object comprising at least one of another custom object and a predefined (standard) object.

12. The machine-readable medium as recited in claim 10, wherein the instructions for carrying out the step of receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database include instructions for carrying out the step of:

receiving a pre-defined (standard) object having at least one relationship to at least one other object indicated by at least one user defined (custom) field, the at least one other object comprising at least one of a user defined (custom) object and another predefined (standard) object.

13. The machine-readable medium as recited in claim 10, wherein the instructions for carrying out the step of storing the relationship information to an index table include instructions for carrying out the step of:

storing relationship information in a multi-way uniquely indexed table.

14. The machine-readable medium as recited in claim 13, wherein the instructions for carrying out the step of storing relationship information in a multi-way uniquely indexed table include instructions for carrying out the step of:

storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction using the same index table.

15. The machine-readable medium as recited in claim 14, wherein the instructions for carrying out the step of storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction using the same index table include instructions for carrying out the step of:

storing relationship information in the index table based on the organization id, relationship id and source entity id, and also by organization id, relationship id, and target entity id.

16. The machine-readable medium as recited in claim 13, wherein the instructions for carrying out the step of storing relationship information in a multi-way uniquely indexed table include instructions for carrying out the step of:

storing multiple indexes enabling traversing of multiple relationships in either a source entity to target entity direction or a target entity to source entity direction regardless of the original source table.

17. The machine-readable medium as recited in claim 10, wherein the instructions for carrying out the step of storing the relationship information to an index table include instructions for carrying out the step of:

storing a target entity id with a set of custom fields in the main table and in the index table.

18. The machine-readable medium as recited in claim 17, wherein the instructions for carrying out the step of storing a target entity id with a set of custom fields in the main table and in the index table include instructions for carrying out the step of:

applying relationships to standard objects

19. An apparatus for storing relationship information for an information object in a database system, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database, the plurality of portions comprising a single table of the database (“

main table”

), the information object relating to at least one other information object by relationship information identifying the other information object in the database; and

storing the relationship information to an index table (“

index table”

) enabling locating information objects related to the information object received without searching the main table, once the information object is stored in the main table.

20. A method for transmitting code for storing relationship information for an information object in a database system on a transmission medium, the method comprising:

transmitting code for receiving an information object to store in a portion of a database accessible to a tenant of a plurality of tenants having access to a plurality of other portions of the database, the plurality of portions comprising a single table of the database (“

main table”

), the information object relating to at least one other information object by relationship information identifying the other information object in the database; and

transmitting code for storing the relationship information to an index table (“

index table”

) enabling locating information objects related to the information object received without searching the main table, once the information object is stored in the main table.