Custom entities and fields in a multi-tenant database system

• US 10,713,230 B2
• Filed: 07/11/2018
• Issued: 07/14/2020
• Est. Priority Date: 04/02/2004
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Weissman, Craig, Wong, Simon
• Primary Examiner(s): Harper, Eliyah S.
• Application Number:
  US16/032,405
• Publication Number:
  US 20180322153A1
• Time in Patent Office: 734 Days
• Field of Search: None
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/2462 Approximate or statistical queries
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06Q 10/063112 Skill-based matching of a person or a group to a task

Abstract

Systems and methods for hosting variable schema data such as dynamic tables and columns in a fixed physical database schema. Standard objects, such as tables are provided for use by multiple tenants or organizations in a multi-tenant database system. Each organization may add or define custom fields for inclusion in a standard object. Custom fields for multiple tenants are stored in a custom data column within the object data structure, and this single custom data column may contain different data types for each tenant.

Claims

1. A method comprising:

defining, at a server system that is communicatively coupled to at least one storage device, a multi-tenant data structure in the at least one storage device including a data table having a plurality of data columns and a plurality of rows, wherein at least two of the rows of the data table are each specific to different tenants and store data for a corresponding one of the different tenants;

receiving, at the server system from a first tenant a first definition for a first data column of the plurality data columns, the first definition designating a first data field of the first data column for storing data that is of a first data type,

receiving, at the server system from a second tenant a second definition for the data column, the second definition designating a second data field of the first data column for storing data that is of a second data type, wherein the second data type is different than the first data type;

storing in metadata of the multi-tenant data structure, at the at least one storage device by the server system, the first definition for the first data column and the second definition for the first data column by;

storing, in the metadata at the at least one storage device, an identifier of the first tenant in association with an identifier of the first data column and an identifier of the first data type, and

storing, in the metadata at the at least one storage device, an identifier of the second tenant in association with the identifier of the first data column and an identifier of the second data type;

receiving, by the server system from the first tenant, a first data value of the first data type to be stored in the first data column;

storing, at the at least one storage device by the server system, the first data value of the first data type received from the first tenant using the first data field of the first data column;

receiving, by the server system from the second tenant, a second data value of the second data type to be stored in the first data column; and

storing, at the at least one storage device by the server system, the second data value of the second data type received from the second tenant using the second data field of the first data column.

2. The method of claim 1, further comprising:

when the first data field has been flagged for indexing, storing, in the metadata at the at least one storage device, an indication that the first data field has been flagged for indexing; and

when the second data field has been flagged for indexing, storing, in the metadata at the at least one storage device, an indication that the second data field has been flagged for indexing.

3. The method of claim 1, wherein the first definition and the second definition are stored in the metadata at the at least one storage device using an extensible markup language (XML) format.

4. The method of claim 1, wherein a second data column of the plurality of data columns of the data table is specific to an identifier of one of the different tenants, such that a third data field of the second data column in a first row specific to the first tenant stores an identifier of the first tenant and a fourth data field of the second data column in a second row specific to the second tenant stores an identifier of the second tenant.

5. The method of claim 1, wherein the first data type and the second data type are selected from the group consisting of:

a string, a number, a date, and a picklist.

6. The method of claim 1, further comprising:

accessing, at the at least one storage device communicatively coupled to the server system, to the first data value stored using the first data field by reading the first data type stored in the metadata; and

providing, to the server system, the first data value in a format indicated by the first data type.

7. The method of claim 6, further comprising:

determining, at the server system, the first data type from the metadata based on the identifier of the first tenant and the identifier of the data column.

8. The method of claim 6, further comprising:

restricting, by the server system, access to the first data value stored in the at least one storage device to the first tenant.

9. The method of claim 1, further comprising:

accessing, by the server system, the second data value stored at the at least one storage device using the second data field by reading the second data type stored in the metadata; and

providing, at the server system, the second data value in a format indicated by the second data type.

10. The method of claim 9, further comprising:

determining, at the server system, the second data type from the metadata based on the identifier of the second tenant and the identifier of the data column.

11. The method of claim 8, further comprising:

restricting, by the server system, access to the second data value stored in the at least one storage device to the second tenant.

12. The method of claim 1, further comprising:

storing, at the at least one storage device, a third row in the data table that stores data specific to a third tenant.

13. The method of claim 12, further comprising:

storing, at the at least one storage device, a null value in a field of the third row corresponding to the data column when a definition for the data column is not received from the third tenant.

14. The method of claim 1, wherein the data table further comprises at least one second data column having a standard data type for storing data of a same data type for the tenants.