Method for safeguarding the integrity of a relational database in case of structural transaction execution

• US 8,521,698 B2
• Filed: 12/20/2010
• Issued: 08/27/2013
• Est. Priority Date: 12/18/2009
• Status: Expired due to Fees

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Solimano, Marco, Piccioli, Giulia
• Primary Examiner(s): Lee, Wilson
• Assistant Examiner(s): Le, Jessica N
• Application Number:
  US12/973,161
• Publication Number:
  US 20110153574A1
• Time in Patent Office: 981 Days
• Field of Search: None
• US Class Current: 707/687
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

A method enables an administration of resources (content) in web packages. By automatically adding a prefix to a resource name causing a name conflict, even resources having the same name can be handled when installing a new web package by a virtual file system mapping the resources to which a prefix has been added to the physical content required for the web application.

Claims

1. A computer implemented method for safeguarding integrity of a relational database in case of structural transaction execution in object relational mapping saving, the method comprising:

on a computer, starting an editing session on an application, the editing session copying a data structure of the application and labeling an original version of the data structure as a current version used and labeling a copied version of the data structure as an editing version, the application being for a structural database transaction to be executed, the application including a set of data structures;

during the editing session on the computer, editing any change to the data structure in the editing version of the data structure;

closing the editing session on the computer by saving the editing version of the data structure to the relational database;

during the saving of the editing version on the computer, installing the editing version of the data structure to the relational database thereby removing the original version of the data structure from the relational database and removing the labeling of a former editing version;

on the computer, starting a second editing session on the application, the second editing session copying a second data structure of the application and labeling an original version of the second data structure as a current version used and labeling a copied version of the second data structure as an editing version;

during the second editing session on the computer, editing any change to the second data structure in the editing version of the second data structure;

closing the second editing session on the computer by discarding the editing version of the data structure; and

during the discarding of the editing version, deleting the editing version and removing the labeling of the original version of the data structure.

2. The method according to claim 1, which further comprises executing the editing session either in a locked mode or an unlocked mode wherein the locked mode does allow any read-action but does not allow any write-action on the application for which the editing session is open, and the unlocked mode allows any read-action and write-action on the application for which the editing session is open.

3. The method according to claim 1, which further comprises during the editing session, checking any change when modifications are issued against data structure inconsistencies, including uniqueness of data structure keys.

4. The method according to claim 1, wherein for the saving of the editing version to the relational database, any user connected to the data structure of the application is disconnected prior to an installation of the editing version to the relational database.

5. The method according to claim 2, wherein in a case of the editing session in the unlocked mode, changes made to the data structure of the application during the editing session are discarded in case of an inconsistency with the data structure of the current version.

6. The method according to claim 1, which further comprises:

on the computer, starting a third editing session on the application, the third editing session copying a third data structure of the application and labeling an original version of the third data structure as a current version used and labeling a copied version of the third data structure as an editing version;

during the third editing session on the computer, editing any change to the third data structure in the editing version of the third data structure;

closing the third editing session on the computer by suspending the editing version of the data structure; and

during the suspending of the editing version, storing the editing version temporarily, keeping the original version of the data structure, and removing the labeling of the original version of the data structure.

7. A computer implemented method for safeguarding integrity of a relational database in case of structural transaction execution in object relational mapping saving, the method comprising:

on a computer, starting an editing session on an application, the editing session copying a data structure of the application and labeling an original version of the data structure as a current version used and labeling a copied version of the data structure as an editing version, the application being for a structural database transaction to be executed, the application including a set of data structures;

during the editing session on the computer, editing any change to the data structure in the editing version of the data structure;

closing the editing session on the computer by saving the editing version of the data structure to the relational database;

during the saving of the editing version on the computer, installing the editing version of the data structure to the relational database thereby removing the original version of the data structure from the relational database and removing the labeling of a former editing version;

on the computer, starting a second editing session on the application, the second editing session copying a second data structure of the application and labeling an original version of the second data structure as a current version used and labeling a copied version of the second data structure as an editing version;

during the second editing session on the computer, editing any change to the second data structure in the editing version of the second data structure;

closing the second editing session on the computer by suspending the editing version of the data structure; and

during the suspending of the editing version, storing the editing version temporarily, keeping the original version of the data structure, and removing the labeling of the original version of the data structure.