TOC PREV NEXT INDEX



RMS data storage operations


This option allows the user to create code which interacts with record stores, which are the objects that MID-enabled devices use for persistent storage. The options include

Before the MIDlet can interact with a record store, you must open a record store. A record store must have a name which is unique within the MIDlet suite. There is an option to automatically create a record store if it does not already exist. The Code Sourcerer can generate code which is available in the current code area only or which is available to the entire MIDlet.

When the MIDlet is finished with a record store, it is important to close it. The close a record store option will write the needed code. Note that if the Code Sourcerer created code available to the entire MIDlet, it already added the code to close a record store.

The Sourcerer also has options to add a record to a record store, which will add a new record to the end of a record store. You can also set a record of a record store, and read a record or all the records from the record store. You can delete a record or all the records from the record store. There is also an option to get the number of records currently in a record store.

Records may be manipulated as Strings, as byte arrays, or as data sets. A data set is simply a number of associated objects which can be added to a single record. This is a good way to save related data in the same record.

In addition to records, record stores have a version. This version is automatically updated whenever a record is added, deleted, or set in a record store. Record stores also hold a date stamp corresponding to the last time of modification. These and other properties can be retrieved from the remaining Code Sourcerer options.


Data Representations, Inc.
http://www.datarepresentations.com
support@datarepresentations.com
sales@datarepresentations.com
TOC PREV NEXT INDEX