DATABASE NAVIGATION OF CHANGES AT COMMIT TIME

• US 20130268503A1
• Filed: 04/06/2012
• Published: 10/10/2013
• Est. Priority Date: 04/06/2012
• Status: Abandoned Application

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Singh, Harpreet, Budithi, Damodara R., Shankar, Gopal, Casey, Lawrence Peter
• Application Number:
  US13/441,018
• Publication Number:
  US 20130268503A1
• Time in Patent Office: Days
• US Class Current: 707/703
• CPC Class Codes: G06F 16/235 Update request formulation

Abstract

An exemplary database management device includes a database storage memory for storing database information. A user access memory at least temporarily stores information to be included in the database. At least a portion of the user access memory is configured to operate as a database manager that allows a user to indicate an intended change to the database information. The database manager places the intended change into the user access memory and determines whether the intended change complies with a criterion responsive to the user attempting to implement the intended change. The database manager makes the intended change to the database information in the database storage memory if the intended change complies with the criterion. The database manager provides an indication that the intended change will not be made to the database and the database storage memory if the intended change does not comply with the criterion.

Claims

1. A database management device, comprising:

a database storage memory for storing database information;

a user access memory for at least temporarily storing information to be included in the database, at least a portion of the user access memory being configured to operate as a database manager that

places an intended change to the database information into the user access memory,

determines whether the intended change in the user access memory complies with at least one criterion for information included in the database responsive to an attempt to implement the intended change to the database, and

makes the intended change to the database information in the database storage memory if the intended change complies with the criterion or provides an indication that the intended change will not be made to the database in the database storage memory if the intended change does not comply with the criterion.

2. The database management device of claim 1, wherein the database manager implements a call back function that includes the at least one criterion responsive to the attempt to implement the intended change in the database in the database storage memory.

3. The database management device of claim 2, wherein a transaction includes the intended change and the database manager implements the call back function while the transaction is active and before the intended change is made in the database in the database storage memory.

4. The database management device of claim 3, wherein the database manager implements the call back function as part of a commit operation of the active trans action.

5. The database management device of claim 3, wherein the transaction includes a plurality of intended changes and the database manager provides an indication that none of the plurality of intended changes will be made if any of the intended changes does not satisfy the at least one criterion.

6. The database management device of claim 1, wherein

the user access memory includes a user data area;

the database manager establishes a record of an operation corresponding to the intended change in the user data area; and

the database manager uses the record for determining whether the intended change satisfies the at least one criterion.

7. The database management device of claim 6, wherein the record in the user data area comprises an indication of at least each of

a table identifier,

an operation type for effecting the intended change,

a location of a new record containing an indication of the intended change, and

a location of an old record containing an indication of information in the database that will be changed as a result of the intended change.

8. The database management device of claim 7, wherein

there are a plurality of intended changes;

the database manager establishes a separate record for each of the intended changes; and

the database manager uses each of the records in an iterative process for determining that each of the intended changes satisfies the at least one criterion.

9. The database management device of claim 1, wherein the user access memory comprises volatile memory.

10. The database management device of claim 9, wherein the database storage memory comprises non-volatile memory.

11. A method of managing a database, comprising the steps of:

storing database information in a database storage memory;

at least temporarily storing information to be included in the database in a user access memory; and

using a database manager that is at least a portion of the user access memory for

placing an intended change to the database information into the user access memory,

determining whether the intended change in the user access memory complies with at least one criterion for information included in the database responsive to an attempt to implement the intended change to the database, and

making the intended change to the database information in the database storage memory if the intended change complies with the criterion or providing an indication that the intended change will not be made to the database in the database storage memory if the intended change does not comply with the criterion.

12. The method of claim 11, comprising using the database manager for implementing a call back function that includes the at least one criterion responsive to the attempt to implement the intended change in the database in the database storage memory.

13. The method of claim 12, comprising implementing the call back function while a transaction that includes the intended change is active and before the intended change is made in the database in the database storage memory.

14. The method of claim 13, comprising implementing the call back function as part of a commit operation of the active transaction.

15. The method of claim 13, comprising

providing an indication that none of a plurality of intended changes included in the transaction will be made if any of the intended changes does not satisfy the at least one criterion,

or

making all of the plurality of changes to the database in the database storage if all of the intended changes satisfy the at least one criterion.

16. The method of claim 11, comprising

establishing a record of an operation corresponding to the intended change in a user data area included in the user access memory;

and

using the record for determining whether the intended change satisfies the at least one criterion.

17. The method of claim 16, wherein the record in the user data area comprises an indication of at least each of

a table identifier,

an operation type for effecting the intended change,

a location of a new record containing an indication of the intended change, and

a location of an old record containing an indication of information in the database that will be changed as a result of the intended change.

18. The method of claim 17, comprising

establishing a separate record for each of a plurality of intended changes;

and

using each of the records in an iterative process for determining that each of the intended changes satisfies the at least one criterion.

19. The method of claim 11, wherein the user access memory comprises volatile memory.

20. The method of claim 19, wherein the database storage memory comprises non-volatile memory.