Enum WriteOp 

#[non_exhaustive]
pub enum WriteOp<'a> {
    Edge {
        source_id: &'a str,
        target_id: &'a str,
        edge_type: &'a str,
    },
    Concept {
        id: &'a str,
        recorded_at: &'a str,
        branch: &'a str,
    },
    Delete {
        table: &'a str,
    },
    Annotation {
        concept_id: &'a str,
    },
}

What a failing statement was trying to do, so a guard abort can name it.

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.

Edge

Fields

source_id: &'a str

target_id: &'a str

edge_type: &'a str

Concept

Fields

id: &'a str

recorded_at: &'a str

branch: &'a str

The lineage the upsert named, for DbError::CrossLineage (0.14.8). It cannot be read back after the abort, because the row it would have been on was never written.

Delete

Fields

table: &'a str

Annotation

A derived annotation (0.13.3, W7.2, crate::Annotation).

The only WriteOp whose failure is not a RAISE(ABORT). analytics_annotations carries no triggers at all — that is why it is the cheapest bulk table and why its chunk ceiling is the largest (D-058) — so the guard vocabulary abort_kind speaks has nothing to say about it. What it does carry is a foreign key onto concepts, and that is the failure a caller can actually cause.

Fields

concept_id: &'a str