METHOD FOR SAFEGUARDING THE INTEGRITY OF A RELATIONAL DATABASE IN CASE OF STRUCTURAL TRANSACTION EXECUTION

• US 20110153574A1
• Filed: 12/20/2010
• Published: 06/23/2011
• Est. Priority Date: 12/18/2009
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: PICCIOLI, Giulia, SOLIMANO, Marco
• Granted Patent: US 8,521,698 B2
• Time in Patent Office: Days
• 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 method for safeguarding integrity of a relational database in case of structural transaction execution in object relational mapping saving, which comprises the steps of:

a) creating an application for a structural database transaction to be executed, the application containing a set of data structure;

b) starting an editing session on the 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 as an editing version;

c) editing any change to the data structure in the editing version of the data structure;

d) closing the editing session by either saving the editing version of the data structure to the relational database, discarding the editing version of the data structure, or suspending the editing version of the data structure, performing the saving, the discarding and the suspending with the following steps of;

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

d2) during the discarding of the editing version, deleting the editing version and removing the labeling of the original version of the data structure; and

d3) 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.

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.