Abstract: A method of insuring the integrity of a plurality of updates brought in real-time to a large production database concurrently used by one or more software applications. The large production database includes a plurality of products participating to the definition of objects. The method first comprises the step of requesting the issuance of a unique filing number associated to a draft state version of the plurality of updates while keeping them invisible to the end-users of the large production database. Then, a set of product items identified as a whole by the unique filing number and on which the updates applies is created or copied in the large production database and gathered under the form of a meta-product on which the plurality of updates is applied. When updating is complete, the meta-product is successively set into a customizable flow of one or more validation states in order to perform a cross-validation of the plurality of updates.

Abstract: A method of integrating large volumes of updates in a database system. Each individual update includes of a coherent set of data records supplied by a data provider. The database system includes a master file repository and an active image repository. The method includes first obtaining for each individual update a unique modification identifier from a logistic table of the database system. The master file repository is then updated with the coherent set of data records of each uniquely identified individual update. A unique commit identifier is further obtained from the logistic table for each individual update that has been committed by the master file. The active image repository is synchronized by successively loading into the active image each individual update. Completion of the propagation of each individual update into the active image repository is achieved when the loading of each corresponding set of data records is committed by the active image.

Abstract: A method of insuring the integrity of a plurality of updates brought in real-time to a large production database concurrently used by one or more software applications is described. The large production database includes a plurality of products participating to the definition of objects. The method first comprises the step of requesting the issuance of a unique filing number associated to a draft state version of the plurality of updates while keeping them invisible to the end-users of the large production database. Then, a set of product items identified as a whole by the unique filing number and on which the updates applies is created or copied in the large production database and gathered under the form of a meta-product on which the plurality of updates is applied. When updating is complete, the meta-product is successively set into a customizable flow of one or more validation states in order to perform a cross-validation of the plurality of updates.

Abstract: A method of insuring the integrity of a plurality of updates brought in real-time to a production database concurrently used by one or more software applications is described. The production database includes a plurality of products participating to the definition of objects. The method first includes requesting the issuance of a unique filing number associated to a draft state version of the plurality of updates while keeping them invisible to the end-users of the production database. Then, a set of product items identified as a whole by the unique filing number are created or copied from the production database and gathered under the form of a meta-product on which the plurality of updates is applied. After updating, the meta-product is successively set into a customizable flow of one or more validation states in order to perform a cross-validation of the plurality of updates.

Abstract: A system for identifying a parameter in a version of a data entity created at a specific time, wherein at a first time the version is an active version and at a second time the version is a previous version, the system comprising: a database for storing the plurality of versions of the data entity as they are created; a cache for storing the first active version of the data entity; wherein when a new version of the data entity is created by updating at least one parameter of the data entity, a new active version replaces the first active version stored in a cache and the first active version becomes a previous version stored in the cache; and wherein the new active version includes a list of the or each previous version of the data entity with an associated time at which the version was an active version, such that by identifying the version of the data entity which was active at the specific time the parameter is determined.

Abstract: A method of insuring the integrity of a plurality of updates brought in real-time to a production database concurrently used by one or more software applications is described. The production database includes a plurality of products participating to the definition of objects. The method first includes requesting the issuance of a unique filing number associated to a draft state version of the plurality of updates while keeping them invisible to the end-users of the production database. Then, a set of product items identified as a whole by the unique filing number are created or copied from the production database and gathered under the form of a meta-product on which the plurality of updates is applied. After updating, the meta-product is successively set into a customizable flow of one or more validation states in order to perform a cross-validation of the plurality of updates.

Abstract: A method of integrating large volumes of updates in a database system is described. Each individual update is comprised of a coherent set of data records supplied by a data provider. The database system includes a master file repository and an active image repository. The method comprises the steps of first obtaining for each individual update a unique modification identifier from a logistic table of the database system. The master file repository is then updated with the coherent set of data records of each uniquely identified individual update. A unique commit identifier is further obtained from the logistic table for each individual update that has been committed by the master file. The active image repository is synchronized by successively loading into the active image, in the order specified by the commit identifier, each individual update. Synchronization includes retrieving from the master file repository the coherent set of data records of each uniquely identified individual update.

Abstract: A system for identifying a parameter in a version of a data entity created at a specific time, wherein at a first time the version is an active version and at a second time the version is a previous version, the system comprising: a database for storing the plurality of versions of the data entity as they are created; a cache for storing the first active version of the data entity; wherein when a new version of the data entity is created by updating at least one parameter of the data entity, a new active version replaces the first active version stored in a cache and the first active version becomes a previous version stored in the cache; and wherein the new active version includes a list of the or each previous version of the data entity with an associated time at which the version was an active version, such that by identifying the version of the data entity which was active at the specific time the parameter is determined.