Enum pliantdb_core::connection::AccessPolicy

pub enum AccessPolicy {
    UpdateBefore,
    UpdateAfter,
    NoUpdate,
}

Changes how the view’s outdated data will be treated.

Variants

UpdateBefore

Update any changed documents before returning a response.

UpdateAfter

Return the results, which may be out-of-date, and start an update job in the background. This pattern is useful when you want to ensure you provide consistent response times while ensuring the database is updating in the background.

NoUpdate

Returns the restuls, which may be out-of-date, and do not start any background jobs. This mode is useful if you’re using a view as a cache and have a background process that is responsible for controlling when data is refreshed and updated. While the default UpdateBefore shouldn’t have much overhead, this option removes all overhead related to view updating from the query.