Enum MigrationConflictStrategy 

pub enum MigrationConflictStrategy {
    Drop,
    Raise,
    BackupAndDrop,
}

Sometimes Migrations can’t proceed without having to drop existing data. This allows you to configure, how these cases should be handled.

Variants

Drop

Just drop the data, we don’t care that we have to sync again

Raise

Raise a SledStoreError::MigrationConflict error with the path to the DB in question. The caller then has to take care about what they want to do and try again after.

BackupAndDrop

Default: The entire database is backed up under $path.$timestamp.backup (this includes the crypto store if they are linked), before the state tables are dropped.

Trait Implementations

impl Clone for MigrationConflictStrategy

fn clone(&self) -> MigrationConflictStrategy

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MigrationConflictStrategy

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for MigrationConflictStrategy

fn eq(&self, other: &MigrationConflictStrategy) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Eq for MigrationConflictStrategy

impl StructuralPartialEq for MigrationConflictStrategy