PERSISTENT DATA STORAGE

• US 20120311289A1
• Filed: 05/31/2011
• Published: 12/06/2012
• Est. Priority Date: 05/31/2011
• Status: Abandoned Application

• Current Assignee: Conexant Systems Incorporated (Synaptics Incorporated)
• Original Assignee: Conexant Systems Incorporated (Synaptics Incorporated)
• Inventors: Meiyappan, Somasundaram, Mikkelsen, Carl, Soltan, Aleksander
• Application Number:
  US13/149,747
• Publication Number:
  US 20120311289A1
• Time in Patent Office: Days
• US Class Current: 711/170
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A persistent data storage system comprising a code development system for defining a plurality of memory storage device identifiers. A configuration database system for associating a tag with a database storage address and with one of the memory storage device identifiers. The code development system for recovering data stored in a persistent electronic data memory associated with each of the memory storage device identifiers during initialization of a database. The configuration database for causing code developed by the code development system to cause data stored at the database storage address to be stored in the persistent electronic data memory if the data stored at the database storage address is changed.

Claims

1. A persistent data storage system comprising:

a code development system for defining a plurality of memory storage device identifiers;

a configuration database system for associating a tag with a database storage address and with one of the memory storage device identifiers;

the code development system for recovering data stored in a persistent electronic data memory associated with each of the memory storage device identifiers during initialization of a database; and

the configuration database for causing code developed by the code development system to cause data stored at the database storage address to be stored in the persistent electronic data memory if the data stored at the database storage address is changed.

2. The persistent data storage system of claim 1 wherein a plurality of persistent electronic data memory devices are associated with the plurality of memory storage device identifiers.

3. The persistent data storage system of claim 1 further comprising a locking system for locking access data stored at selected database storage addresses.

4. The persistent data storage system of claim 3 wherein the data stored at selected database storage addresses comprises a first set of data associated with a first lack and a second set of associated with a second lock.

5. The persistent data storage system of claim 4 wherein configuration database system is configured to prevent the first set of data associated with the first lock from being modified if the second set of data associated with the second lock is locked.

6. The persistent data storage system of claim 4 wherein the first set of data associated with the first lock is associated with a first persistent electronic data memory device and the second set of data associated with the second lock is associated with a second persistent electronic data memory device.

7. A method for persistent data storage comprising:

defining a plurality of persistent memory storage device identifiers;

attaching a plurality of tags to a plurality of corresponding database nodes, wherein each tag associates each associated database node with a memory storage device identifier;

retrieving data stored in a plurality of persistent memory storage devices, each persistent memory storage device associated with one of the persistent memory storage device identifiers;

instantiating a database using the data stored in the plurality of persistent memory storage devices by storing data at each of a plurality of nodes of the database based on the tag associated with each node.

8. The method of claim 7 further comprising:

receiving a modification to data stored at one of the plurality of nodes of the database; and

storing the modified data in one of the persistent memory storage devices based on the tag associated with the node.

9. The method of claim 7 wherein a code development system defines the plurality of persistent memory storage device identifiers.

10. The method of claim 7 wherein code generated by a code development system attaches the tag to the database node.

11. The method of claim 8 wherein a configuration database causes code generated by a code development system to store the modified data in one of the persistent memory storage devices.

12. A database system comprising:

a plurality of access keys stored in a first data memory device sector, each access key associated with node value stored in a second data memory device sector wherein the plurality of access keys are names in a hierarchical naming schema;

an access key processor configured to receive an input value and return the associated node value for the input value if the input value matches an access key stored in the first data memory device sector; and

the access key processor associating a visa with each node, wherein the visa is presented to the access key processor in conjunction with the access key to permit access.

13. The database system of claim 12 wherein the hierarchical naming schema is an XML-compliant naming schema.

14. The database system of claim 12 wherein the visa is generated and associated with each node by the access key processor in response to a request to lock a node, and the visa is removed from the node when it is supplied to the access key processor in conjunction with an unlock request.

15. The database system of claim 12 wherein the visa associated with each node applies to all sub-nodes of the hierarchy.

16. The database system of claim 12 wherein an update to a secondary storage media for a node is delayed until the visa associated with the node is removed.

17. The database system of claim 12 wherein a system component requests notification if the database contents associated with a node change, and the notification is delayed until the visa associated with the node is removed.