Enum ConflictAction 

#[non_exhaustive]
pub enum ConflictAction<S: Model, T: Model> {
    DoNothing,
    #[non_exhaustive]
    DoUpdate {
        assignments: Vec<ConflictUpdate<S, T>>,
        where_clause: Option<Box<ConflictCondition<T>>>,
    },
}

What Postgres does when an incoming row conflicts on the ConflictTarget arbiter: DO NOTHING (skip the row) or DO UPDATE SET ... (merge into the existing row using the EXCLUDED pseudo-row for incoming values). Built indirectly by the on_conflict_* builders on InsertSelectStmt.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

DoNothing

Skip the conflicting row, leaving the existing row unchanged (ON CONFLICT ... DO NOTHING).

#[non_exhaustive]

DoUpdate

Merge the conflicting row into the existing one (ON CONFLICT ... DO UPDATE SET ...), optionally guarded by a WHERE clause.

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

assignments: Vec<ConflictUpdate<S, T>>

The SET column = expr assignments; never empty (an empty list is rejected at execution).

where_clause: Option<Box<ConflictCondition<T>>>

Optional WHERE guard; when false Postgres skips the row rather than updating it.

Trait Implementations

impl<S: Model, T: Model> Clone for ConflictAction<S, T>

fn clone(&self) -> Self

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl<S: Model, T: Model> Debug for ConflictAction<S, T>

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

Formats the value using the given formatter.