Persisting Preferences Data

When to Use

The Preferences module provides APIs for processing data in the form of key-value (KV) pairs, and supports persistence of the KV pairs when required, as well as modification and query of the data. You can use Preferences when you want a unique storage for global data. Preferences caches data in the memory, which allows fast access when the data is required. Preferences is recommended for storing small amount of data, such as personalized settings (font size and whether to enable the night mode) of applications.

Working Principles

User applications call Preference through the JS interface to read and write data files. You can load the data of a Preferences persistence file to a Preferences instance. Each file uniquely corresponds to an instance. The system stores the instance in memory through a static container until the instance is removed from the memory or the file is deleted. The following figure illustrates how Preference works.

The preference persistent file of an application is stored in the application sandbox. You can use context to obtain the file path. For details, see Obtaining Application File Paths.

Figure 1 Preferences working mechanism

Constraints

• The key in a KV pair must be a string and cannot be empty or exceed 80 bytes.

• If the value is of the string type, use the UTF-8 encoding format. It can be empty or a string not longer than 8192 bytes.

• The memory usage increases with the amount of Preferences data. The maximum number of data records recommended is 10,000. Otherwise, high memory overheads will be caused.

Available APIs

The following table lists the APIs used for persisting user preference data. For more information about the APIs, see User Preferences.

How to Develop

1. Import the @ohos.data.preferences module.

   import dataPreferences from '@ohos.data.preferences';

1. Obtain a Preferences instance. Read data from a file and load the data to a Preferences instance for data operations.

Stage model:

   import UIAbility from '@ohos.app.ability.UIAbility';
   import { BusinessError } from '@ohos.base';
   import window from '@ohos.window';
   
   let preferences: dataPreferences.Preferences|null = null;
   
   class EntryAbility extends UIAbility {
       onWindowStageCreate(windowStage: window.WindowStage) {
           try {
               let options: dataPreferences.Options = { name: 'myStore' };
               preferences = dataPreferences.getPreferencesSync(this.context, options);
           } catch (err) {
               let code = (err as BusinessError).code;
         		let message = (err as BusinessError).message;
         		console.error(`Failed to get preferences. Code:${code},message:${message}`);
           }
       }
   }

FA model:

   // Obtain the context.
   import featureAbility from '@ohos.ability.featureAbility';
   import { BusinessError } from '@ohos.base';
   
   let context = featureAbility.getContext();
   let preferences: dataPreferences.Preferences|null = null;
   
   try {
       let options: dataPreferences.Options =  { name: 'myStore' };
       preferences = dataPreferences.getPreferencesSync(context, options);
   } catch (err) {
       let code = (err as BusinessError).code;
     	let message = (err as BusinessError).message;
     	console.error(`Failed to get preferences. Code is ${code},message:${message}`);
   }

1. Write data.

Use putSync() to save data to the cached Preferences instance. After data is written, you can use flush() to persist the Preferences instance data to a file if necessary.

NOTE

If the specified key already exists, the putSync() method changes the value. You can use hasSync() to check whether the KV pair exists.

Example:

   try {
     if (preferences.hasSync('startup')) {
       console.info("The key 'startup' is contained.");
     } else {
       console.info("The key 'startup' does not contain.");
       // Add a KV pair.
       preferences.putSync('startup', 'auto');
     }
   } catch (err) {
     let code = (err as BusinessError).code;
     let message = (err as BusinessError).message;
     console.error(`Failed to check the key 'startup'. Code:${code}, message:${message}`);
   }

1. Read data.

Use getSync() to obtain the value of the specified key. If the value is null or is not of the default value type, the default data is returned.

Example:

   try {
     let val = preferences.getSync('startup', 'default');
     console.info(`Succeeded in getting value of 'startup'. val: ${val}.`);
   } catch (err) {
     let code = (err as BusinessError).code;
     let message = (err as BusinessError).message;
     console.error(`Failed to get value of 'startup'. Code:${code}, message:${message}`);
   }

1. Delete data.

Use deleteSync() to delete a KV pair.

Example:

   try {
     preferences.deleteSync('startup');
   } catch (err) {
     let code = (err as BusinessError).code;
     let message = (err as BusinessError).message;
     console.error(`Failed to delete the key 'startup'. Code:${code}, message:${message}`);
   }

1. Persist data.

You can use flush() to persist the data held in a Preferences instance to a file.

Example:

   try {
     preferences.flush((err: BusinessError) => {
       if (err) {
         console.error(`Failed to flush. Code:${err.code}, message:${err.message}`);
         return;
       }
       console.info('Succeeded in flushing.');
     })
   } catch (err) {
     let code = (err as BusinessError).code;
     let message = (err as BusinessError).message;
     console.error(`Failed to flush. Code:${code}, message:${message}`);
   }

1. Subscribe to data changes.

Specify an observer as the callback to return the data changes for an application. When the value of the subscribed key is changed and saved by flush(), the observer callback will be invoked to return the new data.

Example:

   preferences.on('change', (key: string) => {
     console.info('The key' + key + 'changed.');
   });
   // The data is changed from 'auto' to 'manual'.
   preferences.put('startup', 'manual', (err: BusinessError) => {
     if (err) {
       console.error(`Failed to put the value of 'startup'. Code:${err.code},message:${err.message}`);
       return;
     }
     console.info("Succeeded in putting the value of 'startup'.");
     preferences.flush((err: BusinessError) => {
       if (err) {
         console.error(`Failed to flush. Code:${err.code}, message:${err.message}`);
         return;
       }
       console.info('Succeeded in flushing.');
     })
   })

1. Delete a Preferences instance from the memory.

Use deletePreferences() to delete a Preferences instance from the memory. If the Preferences instance has a persistent file, the persistent file and its backup and corrupted files will also be deleted.

NOTE

• The deleted Preferences instance cannot be used for data operations. Otherwise, data inconsistency will be caused.

• The deleted data and files cannot be restored.

Example:

   try {
       let options: dataPreferences.Options = { name: 'myStore' };
       dataPreferences.deletePreferences(this.context, options, (err: BusinessError) => {
           if (err) {
               console.error(`Failed to delete preferences. Code:${err.code}, message:${err.message}`);
               return;
           }
           console.info('Succeeded in deleting preferences.');
       })
   } catch (err) {
       let code = (err as BusinessError).code;
       let message = (err as BusinessError).message;
       console.error(`Failed to delete preferences. Code:${code}, message:${message}`);
   }

你可能感兴趣的鸿蒙文章

harmony 鸿蒙Data Management

harmony 鸿蒙Access Control by Device and Data Level

harmony 鸿蒙Application Data Persistence Overview

harmony 鸿蒙Database Backup and Restoration

harmony 鸿蒙Database Encryption

harmony 鸿蒙Data Management Overview

harmony 鸿蒙Persisting KV Store Data

harmony 鸿蒙Persisting RDB Store Data

harmony 鸿蒙Data Reliability and Security Overview

harmony 鸿蒙Cross-Application Data Sharing