Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Using Arrays in Index Paths
Before Mobile SDK 4.1, index paths supported only maps—in other words, dictionaries or associative arrays. For example, in a path such as a.b.c, SmartStore required both b and c to be maps. Otherwise, when evaluating the path, SmartStore returned nothing.
Example
The following table shows various examples of a.b.c paths and the values returned by a SmartStore query.
| Description | Example soup element | Value for path a.b.c |
|---|---|---|
| No arrays |
|
1 |
| c points to an array (internal node). |
|
|
| b points to an array of maps. Some maps contain the c key. Other maps are ignored. |
|
|
| a points to an array of maps. In some maps, b points to a map containing a key. In other maps, b points to an array of maps. Only values from c keys are returned. |
|
|