Methods and systems for loose coupling between triggers and entities

• US 9,690,808 B2
• Filed: 11/04/2011
• Issued: 06/27/2017
• Est. Priority Date: 12/01/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Ma, Billy, Roy-Faderman, Avrom Irwin
• Primary Examiner(s): Spieler, William
• Application Number:
  US13/289,116
• Publication Number:
  US 20120143837A1
• Time in Patent Office: 2,062 Days
• Field of Search: 706 60
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/24565 Triggers; Constraints

Abstract

A database program includes loose triggers that are not coupled to specific entities at the time the database program is compiled. The database program provides a user interface that allows a user to couple selected entities to the loose triggers or decouple selected entities from loose triggers. The database program validates the entities that are selected by the user for coupling or decoupling and stores the coupled entities as part of the loose trigger definitions in a loose trigger metadata database.

Claims

1. A method for using a database program with loose triggers, the method comprising:

providing by the database program, a first loose trigger;

receiving by the database program, a selection of a first entity from a plurality of entities associated with a plurality of organizations, each entity being a subdivision of an associated organization and being associated with a plurality of databases;

storing by the database program, the selected first entity and the first loose trigger in a metadata database before code associated with the first loose trigger is compiled and the first loose trigger is coupled to one of the plurality of entities; and

coupling the selected first entity with the first loose trigger after the code associated with the first loose trigger has been compiled such that at least the selected first entity of the plurality of entities is coupled to the first loose trigger after the first loose trigger has been compiled, the first loose trigger causing a change to one of the plurality of databases associated with the selected first entity in response to being triggered.

2. The method of claim 1 further comprising:

detecting by the database program, the first entity interacting with a database; and

actuating by the database program, the first loose trigger in response to the detecting the first entity.

3. The method of claim 2 further comprising:

receiving by the database program, a second entity that is selected from the listing of entities, the second entity having a different associated organization than the first entity;

storing by the database program, the second entity with the first loose trigger in the metadata database.

4. The method of claim 3 further comprising:

detecting by the database program, the second entity interacting with the database; and

actuating by the database program, the first loose trigger in response to the detecting of interaction of the second entity with the database.

5. The method of claim 1 further comprising:

validating by the database program, the first entity before storing the first entity with the first loose trigger in the metadata database, the validating comprising determining if the storing violates a trigger rule that limits use of the first loose trigger and allowing the storing when the trigger rule is not violated by the storing.

6. The method of claim 1 further comprising:

invalidating by the database program, the first entity, the invalidating comprising determining if the storing violates a trigger rule that limits use of the first loose trigger; and

preventing by the database program, the storing of the first entity in the metadata database when the trigger rule is violated by the storing.

7. The method of claim 1 further comprising:

displaying by the database program, the trigger program code in a portion of the user interface;

wherein the trigger program code is editable.

8. A computer program product comprising computer-readable program code to be executed by one or more processors when retrieved from a non-transitory machine-readable medium, the program code including instructions to

provide by the database program, a first loose trigger;

receive by the database program, a selection of a first entity from a plurality of entities associated with a plurality of organizations, each entity being a subdivision of an associated organization and being associated with a plurality of databases;

store by the database program, the selected first entity and the first loose trigger in a metadata database before code associated with the first loose trigger is compiled and the first loose trigger is coupled to one of the plurality of entities; and

couple the selected first entity with the first loose trigger after the code associated with the first loose trigger has been compiled such that at least the selected first entity of the plurality of entities is coupled to the first loose trigger after the first loose trigger has been compiled, the first loose trigger causing a change to one of the plurality of databases associated with the selected first entity in response to being triggered.

9. The computer program product as recited in claim 8, the program code including instructions to:

detect by the database program, the first entity interacting with a database; and

actuate by the database program, the first loose trigger in response to the detecting of the first entity.

10. The computer program product as recited in claim 9, the program code including instructions to:

receive by the database program, a second entity that is selected from the listing of entities, the second entity having a different associated organization than the first entity; and

store by the database program, the second entity with the first loose trigger in the metadata database.

11. The computer program product as recited in claim 10, the program code including instructions to:

detect by the database program, the second entity interacting with a database; and

actuate by the database program, the first loose trigger in response to the detecting of interaction of the second entity with the database.

12. The computer program product as recited in claim 8, the program code including instructions to:

validate by the database program, the first entity before storing the first entity as a first loose trigger definition in the metadata database, the program code to validate comprising program code to determine if the storing violates a trigger rule that limits use of the first loose trigger and program code to allow the storing when the trigger rule is not violated by the storing.

13. The computer program product as recited in claim 8, the program code including instructions to:

invalidate by the database program, the first entity, the invalidating comprising determining if the storing violates a trigger rule that limits use of the first loose trigger; and

prevent by the database program, the storing of the first entity with the first loose trigger in the metadata database when the trigger rule is violated by the storing.

14. The computer program product as recited in claim 8, the program code including instructions to:

display by the database program, the trigger program code in a portion of the user interface;

wherein the trigger program code is editable.

15. An apparatus for using a database program with loose triggers, the apparatus comprising:

a processor; and

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

provide by the database program, a first loose trigger;

receive by the database program, a selection of a first entity from a plurality of entities associated with a plurality of organizations, each entity being a subdivision of an associated organization and being associated with a plurality of databases;

store by the database program, the selected first entity and the first loose trigger in a metadata database before code associated with the first loose trigger is compiled and the first loose trigger is coupled to one of the plurality of entities; and

couple the selected first entity with the first loose trigger after the code associated with the first loose trigger has been compiled such that at least the selected first entity of the plurality of entities is coupled to the first loose trigger after the first loose trigger has been compiled, the first loose trigger causing a change to one of the plurality of databases associated with the selected first entity in response to being triggered.

16. The apparatus as recited in claim 15, the one or more stored sequences of instructions, when executed, will cause the one or more processors to:

detect by the database program, the first entity interacting with a database; and

actuate by the database program, the first loose trigger in response to the detecting of the first entity.

17. The apparatus as recited in claim 16, the one or more stored sequences of instructions, when executed, will cause the one or more processors to:

receive by the database program, a second entity that is selected from the listing of entities, the second entity having a different associated organization than the first entity; and

store by the database program, the second entity with the first loose trigger in the metadata database.

18. The apparatus as recited in claim 17, the one or more stored sequences of instructions, when executed, will cause the one or more processors to:

detect by the database program, the second entity interacting with a database; and

actuate by the database program, the first loose trigger in response to the detecting of the second entity.

19. The apparatus as recited in claim 17, the one or more stored sequences of instructions, when executed, will cause the one or more processors to:

invalidate by the database program, the first entity, the invalidating comprising determining if the storing violates a trigger rule that limits use of the first loose trigger; and

prevent by the database program, the storing of the first entity as the trigger definition in the metadata database when the trigger rule is violated by the storing.

20. The apparatus as recited in claim 15, the one or more stored sequences of instructions, when executed, will cause the one or more processors to:

validate by the database program, the first entity before storing the first entity as a trigger definition in the metadata database, the program code to validate comprising program code to determine if the storing violates a trigger rule that limits use of the first loose trigger and program code to allow the storing when the trigger rule is not violated by the storing.

21. The apparatus as recited in claim 15, the processor further carrying out the steps of:

display by the database program, the trigger program code in a portion of the user interface;

wherein the trigger program code is editable.