Persisted Search Folder Items

[This is preliminary documentation and subject to change.]

When you create a persisted search folder, you specify a SQL command that the Web Store uses to populate the folder with items. After the folder has been populated, links to all items that match your request are placed into the folder. Additionally, each item's complete set of properties is also available. Because of this, the list of properties you specify when creating the persisted search folder does not limit what properties you can access or search for within the search folder itself. You can issue PROPGET and SEARCH commands for items in the folder in the normal way. The most important aspect of the SQL command used to construct the folder is the WHERE clause condition.

If you issue a SELECT * search command with a scope containing the persisted search folder, you receive the properties defined by the original containing folder's schema. That is, the list of properties returned by SELECT * for a persisted search folder is not controlled by the search folder's schema, but rather the item's containing folder itself. This additionally holds when you issue a PROPGET command. In summary, the normal schema rules for items in a folder still hold as if the items were being accessed in their actual containing folder.

You cannot add new items manually to a persisted search folder. If you issue a PUT, POST, or a normal MKCOL command for an item within the search folder, the Web Store will return an error. You can nest search folders however.

See Also