mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the directory has to be closed/released
fid the folder identifier referencing the folder to close

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the messagewill be created
parent_fid the parent folder identifier
mid the message identifier to create

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the message's to be located is stored
mid the message identifier of the folder to delete
deletion_type the type of deletion (MAPISTORE_SOFT_DELETE or MAPISTORE_PERMANENT_DELETE)

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the folder will be searched for
parent_fid the parent folder identifier
name the name of the folder to search for
fid the fid (result)

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend
table_type the type of table (folders or messges)
fid the folder identifier where the search takes place
proptag the MAPI property tag to retrieve value for
pos the record position in search results
data pointer on pointer to the data the function returns

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where properties will be fetched
fmid the identifier referencing the message/folder
type the object type (folder or message)
properties pointer to the list of properties to fetch
aRow pointer to the SRow structure

mstore_ctx pointer to the mapistore context
username the name of the account where to look for the indexing database
fmid the folder/message ID to search
_flist the list of folders (result)

Note:

This function is useful for the emsmdb provider when we are trying to open a folder/message using an InputHandleIdx referencing the store object. In such situation, no context ID is available since the store object access openchange.ldb.

It means we need to retrieve the list of folders to the item within the mapistore context and rely on an existing parent (if opened) or opens everything from the top parent if none is available.

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the indexing database to update
fid the fid to remove
deletion_type the type of deletion (MAPISTORE_SOFT_DELETE or MAPISTORE_PERMANENT_DELETE)

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the indexing database to update
mid the mid to remove
deletion_type the type of deletion (MAPISTORE_SOFT_DELETE or MAPISTORE_PERMANENT_DELETE)

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the directory will be created
parent_fid the parent folder identifier
fid the folder identifier for the new folder
aRow pointer to MAPI data structures with properties to be added to the new folder

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the directory will be opened
parent_fid the parent folder identifier
fid folder identifier to open

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the directory will be opened
parent_fid the parent folder identifier
mid the message identifier to open
msg pointer to the mapistore_message structure (result)

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend
fmid a folder or message identifier
type the type of fmid, either MAPISTORE_FOLDER or MAPISTORE_MESSAGE

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend
parent_fid the parent folder identifier
fid the folder identifier representing the folder to delete
flags flags that control the behaviour of the operation

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the message's changes will be saved
mid the message identifier to save
flags flags associated to the commit operation

The mapping path can be set unless id_mapping_context is initialized. If path is NULL and mapping path is not yet initialized, then mapping_path will be reset to its default value when the initialization routine is called.

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where properties will be stored
fmid the identifier referencing the message/folder
type the object type (folder or message)
aRow pointer to the SRow structure

mstore_ctx pointer to the mapistore context
context_id the context identifier referencing the backend where the message will be submitted
mid the message identifier representing the message to submit
flags flags associated to the submit operation

mdb_ctx pointer to the mapistore database context
index the special folder index
username the username for which we want to retrieve the uri
uri the uri namespace for the backend we want to use
namespace_uri pointer to the resulting namespace uri (return value)

The special folder is specified by the index parameter. For example to create the 'inbox' folder, pass MDB_INBOX.

This function obtains a range of folder / message identifiers. Conceptually you specify how many identifiers you want, and are provided a contiguous block of identiers (in terms of a start and end, which are inclusive).

This function is a wrapper over mapistore_get_new_allocation_range from mapistore_processing.c

Parameters:

mdb_ctx pointer to the mapistore database context
range the number of IDs to allocate
range_start pointer to the first ID of the range to return
range_end pointer to the last ID of the range to return