Method for Managing Simultaneous Modification of Database Objects During Development

• US 20100114967A1
• Filed: 09/03/2007
• Published: 05/06/2010
• Est. Priority Date: 09/04/2006
• Status: Active Grant

• Current Assignee: D.B. Maestro Ltd.
• Original Assignee: Extreme Technologies, Inc.
• Inventors: Ozeri, Roy, Yaniv, Yehuda
• Granted Patent: US 8,768,966 B2
• Time in Patent Office: Days
• US Class Current: 707/785
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries

Abstract

The present invention relates to a method for preventing the simultaneous modification of the same database object in a shared database by more than one user during the database development stage comprising the steps of: (a) creating security roles for said users, wherein each of the security roles has a modification permission set for denying or granting at least one modification permission to at least one said database object; (b) assigning each of said security roles to each of said users; (c) providing means for said users to request said modification permission to said database object; (d) receiving said request from a first user for said modification permission to said at least one database object; (e) determining that said security roles of said users, excluding the security role of first user, are set to deny said modification permissions to said object; (f) updating said security role of said first user to grant said modification permission to said object; (g) allowing said first user to modify said object; (h) receiving a termination notification from said first user for concluding said modification permission to said object; and (i) updating said security role of said first user to cease said modification permission to said object.

Claims

1. A method for preventing the simultaneous modification of the same database object(s) in a shared database by more than one user during the database development stage comprising the steps of:

a. creating security roles for said users, wherein each of the security roles has a modification permission set for denying or granting at least one modification permission to at least one of said database object;

b. assigning each of said security roles to each of said users;

c. providing means for said users to request said modification permission to said database object;

d. receiving said request from a first user for said modification permission to said at least one database object;

e. determining that said security roles of the remaining user(s), are set to deny said modification permissions to said object;

f. updating said security role of said first user to grant said modification permission to said object;

g. allowing said first user to modify said object;

h. receiving a termination notification from said first user for concluding said modification permission to said object; and

i. updating said security role of said first user to cease said modification permission to said object.

2. A method according to claim 1, where the first user is allowed to modify the object in the shared database.

3. A method according to claim 1, where the first user is allowed to modify the object in a cloned database which corresponds to the object of the shared database.

4. A method according to claim 3, where the object of the cloned database is updated to correspond to the object of the shared database prior to allowing the first user to modify said object of said cloned database.

5. A method according to claim 3, where the object of the shared database is updated with the first user'"'"'s modifications after receiving a termination notification from said first user.

6. A method according to claim 1, where the means for requesting modification permission to a database object is a software program installed on the computer of the user.

7. A method according to claim 1, where the means for requesting modification permission to a database object is an extension installed on the IDE of the user.

8. A method according to claim 1, where the users are notified that the object has been modified after the first user has modified the object and sent a termination notification.

9. A method according to claim 1, where the first user is notified of the database object'"'"'s dependencies after said first user'"'"'s request to modify said object.

10. A method for preventing the simultaneous modification of the same database object in a shared database by more than one user during the database development stage comprising the steps of:

a. providing a DDL trigger, which automatically executes in response to a DDL event;

b. providing a list of said users for said DDL trigger, for listing which of said users is granted a modification permission for which of said database objects;

c. providing means for said users to request a modification permission to said database object;

d. receiving said request from a first user for modification permission to said database object;

e. determining that said database object modification permission has not been granted to a second user;

f. marking, in said list, that said first user has been granted modification permission of said database object;

g. allowing said user to modify said object by permitting commit execution on the DB object modifications;

h. blocking the remaining users, from performing modifications by performing a “

roll back”

action when users perform modifications on said database object;

i. receiving a termination notification from first user for concluding said modification permission to said object; and

j. updating said list by dropping said first user from the users'"'"' permission list of that object.

11. A method for preventing the simultaneous modification of the same database object in a shared database by more than one user during the database development stage comprising the steps of

a. setting said database security tables or access lists to deny modification permissions from all said users;

b. providing means for said users to request said modification permission to said at least one database object;

c. receiving said request from a first user for a modification permission to said at least one database object;

d. determining that said modification permission to said database object has not been granted to a second user;

e. updating said security tables or other relevant resources to grant said modification permission of said database object to said first user;

f. allowing said first user to modify said object;

g. receiving a termination notification from first user for concluding said modification permission to said object; and

h. updating said security tables or other relevant resources to cease said modification permission of said database object to said first user.