C H A P T E R 1 1
Data Storage and Retrieval
Using Newton Data Storage Objects
method retrieves the value of a specified slot in the store information frame. Its
store method, writes the value of a specified slot in this frame.
This section discusses the functions and methods used to work with soup objects.
Individual entries in soups and union soups are manipulated by means of queries,
cursors, and entry functions, as described in subsequent sections of this chapter.
This section describes procedures for
creating soups and indexes
retrieving existing soups
indexing existing soups
reading and writing soup data
accessing information about the soup itself and the store on which it resides
When creating soups, you need to follow certain naming conventions in order to
avoid name collisions with other applications' soups. Following these conventions
also makes your own soups more easily identifiable.
If your application creates only one soup, you can use your package name as the
name of its soup. Your package name is created by using a colon (
) to append
your package's Extras Drawer name to your unique developer signature. For
example, if your developer signature is
and you are creating a
package that appears in the Extras Drawer with the name
these two values produces the
If your application creates multiple soups, use another colon, followed by your
package name, as a suffix to a descriptive soup name. For example,
acceptable soup names unlikely to duplicate those used by other applications.
Normally, each soup appears under its own icon in the Extras Drawer. If your
application creates multiple soups, it is recommended that you group them under a
single Extras Drawer icon. For more information, see "About Icons and the Extras
Drawer" on page 19-38 in Chapter 19, "Built-in Applications and System Data."
For additional information regarding naming conventions for your developer
signature and other items, see "Developer Signature Guidelines" on page 2-9 in
Chapter 2, "Getting Started."