Destructor.

Adds a new landmark to the database and returns its ID.

This function requires ReadUserData and WriteUserData capabilities.

Cancels a call to NotifyDatabaseEvent .

This function requires ReadUserData capability.

Compacts the landmark database.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

The client takes ownership of the returned operation object.

This function requires ReadUserData and WriteUserData capabilities.

Returns a URI which points to the landmark database storage.

The URI may point to a file in the terminal file system or on a remote file.

The client takes ownership of the returned descriptor.

Exports a number of landmarks.

The client must also provide a list of the landmarks which should be exported. If one of the landmarks are not found in the database, the returned operation fails with error code KErrNotFound.

The client does not have to add any landmarks to the encoder object. This function will add the ones specified in the ID array.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that only a subset of the landmarks have been exported.

The client takes ownership of the returned operation object.

When all landmarks have been exported the client must finalize encoding by calling CPosLandmarkEncoder::FinalizeEncodingL .

This function requires ReadUserData capability.

Import a set of landmarks.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that only a subset of the landmarks have been imported.

The client takes ownership of the returned operation object.

After completion ImportedLandmarksIteratorL can be called to retrieve the IDs of the added landmarks.

The NextStep function in the operation object cannot be executed synchronously using User::WaitForRequest. Doing so may cause the operation to hang. NextStep must be run using an active object for this operation.

This function requires ReadUserData and WriteUserData capabilities.

Import a set of landmarks.

In this overload of the function, the client can pass an array defining a subset of the landmarks in the parser object. This way the client can select to import only a part of the landmark content.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that only a subset of the landmarks have been imported.

The client takes ownership of the returned operation object.

After completion ImportedLandmarksIteratorL can be called to retrieve the IDs of the added landmarks.

The NextStep function in the operation object cannot be executed synchronously using User::WaitForRequest. Doing so may cause the operation to hang. NextStep must be run using an active object for this operation.

This function requires ReadUserData and WriteUserData capabilities.

Returns an object for iterating the landmarks added in an import operation.

To import landmarks ImportLandmarksL is used.

If ImportedLandmarksIteratorL is called before the ImportLandmarksL operation has completed, the iterator will iterate the landmarks imported so far. Landmarks imported after the iterator is obtained will not affect the iterator. A new iterator must be obtained to iterate these new landmarks.

The client takes ownership of the returned iterator object.

Initializes the database.

This function may have to be called right after the database is opened. IsInitializingNeeded can be called to find out if initialization is needed.

If the database becomes damaged, the client can call InitializeL to try to recover the database.

It is ok to call even if initialization is not needed. In this case, the operation will not do anything.

If the database needs to be initialized, the client must call InitializeL , otherwise the database may not be possible to access. Access functions may leave with KErrPosLmNotInitialized.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that the database is not yet initialized.

The client takes ownership of the returned operation object.

This function requires ReadUserData capability.

Checks if the database is in need of initialization.

If the database needs to be initialized, the client must call InitializeL , otherwise the database may not be possible to access. Access functions may leave with KErrPosLmNotInitialized.

Initialization may be needed also if the database becomes damaged. The client can then try to call InitializeL to try to recover the database.

Returns an object for iterating the landmarks in the database.

The client takes ownership of the returned iterator object.

This function requires ReadUserData capability.

Returns an object for iterating the landmarks in the database.

This overload of the iterator function takes a sort preference object as input. The sort preference object specifies how the landmarks should be sorted by the iterator. Only sorting by landmark name is supported.

The client takes ownership of the returned iterator object.

This function requires ReadUserData capability.

Listens for database events.

This function is asynchronous and it will complete the request status when an event occurs. At this time aEvent input parameter is updated and the client can read event information from it.

Event listening can be cancelled by calling CancelNotifyDatabaseEvent .

This function requires ReadUserData capability.

Opens the default landmark database.

The client takes ownership of the returned database handle.

The database may have to be initialized before it can be used, see IsInitializingNeeded and InitializeL .

This function requires ReadUserData capability.

Opens a specific landmark database.

The client refers to a database by URI. The URI consists of a protocol specifier and the database location: "protocol://location". If the client does not specify a protocol, "file://" will be assumed.

For local landmark databases, the URI consists of the drive and the database file name, e.g. "c:landmarks.ldb". The path cannot be specified by the client. The extension of the database file name must be "ldb" otherwise the client will get the error KErrArgument.

If the client specifies a local database and does not specify the drive letter, e.g. "landmarks.ldb", default database drive will be assumed.

The client takes ownership of the returned database handle.

The database may have to be initialized before it can be used, see IsInitializingNeeded and InitializeL .

This function requires ReadUserData capability.

Returns the partial read parameters for this database handle.

Partial read parameters are used to define which landmark data should be returned when ReadPartialLandmarkLC is called.

The client takes ownership of the returned parameter object.

Reads partial data from a set of landmarks in the database.

Note that the returned data may be very big if all attributes in each landmark are requested. A typical use for this function is to retrieve the names for a set of landmarks.

When the request is completed, the result can be retrieved by calling TakePreparedPartialLandmarksL .

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

The client takes ownership of the returned operation object.

While preparing landmark information, this operation will acquire a read-lock on the database.

This function requires ReadUserData capability.

Reads a landmark from the database.

This function requires ReadUserData capability.

Reads partial data from a landmark in the database.

The client takes ownership of the returned landmark object.

This function requires ReadUserData capability.

Removes all landmarks from the database.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that only a subset of the landmarks have been deleted.

The client takes ownership of the returned operation object.

While removing landmarks, this operation will acquire a write-lock on the database.

This function requires ReadUserData and WriteUserData capabilities.

Removes a landmark from the database.

This function requires ReadUserData and WriteUserData capabilities.

Removes a set of landmarks from the database.

The function returns an operation object which can be run in incremental mode. If it is run incrementally the client can supervise the progress of the operation.

If the CPosLmOperation object is deleted before the operation is complete, it is possible that only a subset of the landmarks have been deleted.

The client takes ownership of the returned operation object.

While removing landmarks, this operation will acquire a write-lock on the database.

This function requires ReadUserData and WriteUserData capabilities.

Sets the partial read parameters for this database handle.

Partial read parameters are used to define which landmark data should be returned when ReadPartialLandmarkLC is called.

Returns size information for the database.

This function requires ReadUserData capability.

Fetches the result from a call to PreparePartialLandmarksL .

If reading a landmark failed during preparation, the corresponding pointer value in the returned array will be NULL. For instance, reading can fail if the specified ID does not exist in the database.

The client takes ownership of the returned array object including the contained landmark objects.

Updates a landmark in the database.

Note that any updates in the database made since the landmark object was read from the database will be overwritten by this operation.

A landmark can contain the IDs of the categories it belongs to. If any of these categories does not exist in the database, the update operation will still complete successfully but the category which was not found will be ignored.

This function requires ReadUserData and WriteUserData capabilities.

Specifies options for importing and exporting landmarks.

Bitmap for specifying a group of transfer options defined by _TAttributes .