Object graph editing context and methods of use

A non-transitory computer program product for managing changes to data, the computer program product being embodied in a computer readable medium and comprising computer instructions for:

• receiving an indication in an object graph manager that a data bearing object expects to undergo a change, wherein the data bearing object includes a programmatic grouping of data and the change includes a modification, an addition, or a removal of associated data, and wherein the object graph manager is external to a database level in a database application;
• registering a change anticipation message memorializing the expected change to a data bearing object in the object graph manager;
• taking a first snapshot of said data bearing object upon receiving the change anticipation message;
• saving the first snapshot in an undo stack;
• identifying the change to said data bearing object once it has occurred;
• and
• receiving an additional event message selected from among a commit message and an undo message, further comprising:
• in the event of a commit message, performing the change to the data bearing object and performing a garbage collection process to the undo stack;
• and
• in the event of an undo message, ignoring the change and retaining the data bearing object in a form represented by a snapshot in the undo stack.

A computer system, comprising:

• a processor configured to:
• receiving an indication in an object graph manager that a data bearing object expects to undergo a change, wherein the data bearing object includes a programmatic grouping of data and the change includes a modification, an addition, or a removal of associated data, and wherein the object graph manager is external to a database level in a database application;
• registering a change anticipation message memorializing the expected change to a data bearing object in the object graph manager;
• taking a first snapshot of said data bearing object upon receiving the change anticipation message;
• saving the first snapshot in an undo stack;
• identifying the change to said data bearing object once it has occurred;
• and
• receiving an additional event message selected from among a commit message and an undo message, further comprising:
• in the event of a commit message, performing the change to the data bearing object and performing a garbage collection process to the undo stack;
• and
• in the event of an undo message, ignoring the change and retaining the data bearing object in a form represented by a snapshot in the undo stack;
• and
• a memory coupled to the processor and configured to provide the processor with instructions.