Browse Prior Art Database

Firmware Upgrade and data management based on a database

IP.com Disclosure Number: IPCOM000200498D
Publication Date: 2010-Oct-15
Document File: 2 page(s) / 47K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention proposes a technique to allow additions, updates/deletes to current tables without lost persistent data and it's integrity. Each database file will have a Secure Hash Algorithm (SHA1) to detect there is a change in the schema, as database server is started. If the server detects there is a change in the SHA1 value , Database code attaches to both the databases files, working copy and new copy, and compare each tables,view,index. New schema changes in the new copy is merged to the working copy, keeping working copy existing data intact.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 85% of the total text.

Page 01 of 2

Firmware Upgrade and data management based on a database

Application persistent Data Management across firmware upgrade across the different level is critical for the server functioning. Normally application developer are left to manage data and it's migration between code and schema changes. This creates overhead for application developers and cause problems if the schema and data version numbering is not handled correctly.

As new functions or new hardware parts are supported, new tables or rows or columns can be added to the database schema. If persistent data has links back to schema, there could be orphan tables or worst invalid relationships.

This disclosure proposes a technique to allow additions, updates/deletes to current tables without lost persistent data and it's integrity. Each database file will have a Secure Hash Algorithm (SHA1) to detect there is a change in the schema, as database server is started. If the server detects there is a change in the SHA1 value , Database code attaches to both the databases files, working copy and new copy, and compare each tables,view,index. New schema changes in the new copy is merged to the working copy, keeping working copy existing data intact.

Flow for checking/creating SHA1 and merging working database copy with the new database copy if needed is displayed.

Flow charts of the proposed method follows, the first one is for the main flow, the second one reflects the merging mechanism. The objective of the merge m...