Struct RequestFieldUpdates 

pub struct RequestFieldUpdates<'a> {

    pub name: Option<&'a str>,
    pub description: Option<&'a str>,
    pub schedule_date: Option<DateTime<Utc>>,
    pub schedule_end: Option<DateTime<Utc>>,
    pub duration: Option<Decimal>,
    pub owner_user_id: Option<Uuid>,
    pub user_id: Option<Uuid>,
    pub asset_id: Option<Uuid>,
    pub priority: Option<&'a str>,
    pub maintenance_type: Option<&'a str>,
    pub recurring: Option<bool>,
    pub repeat_interval: Option<i32>,
    pub repeat_unit: Option<&'a str>,
    pub repeat_type: Option<&'a str>,
    pub repeat_until: Option<NaiveDate>,
}

The recurrence/descriptive fields update_request may change. None leaves the column unchanged (COALESCE at the DB). The lifecycle columns — stage_id, kanban_state, close_date, the successor markers — are deliberately absent: they belong to the transition verb and the spawn engine.

Fields

name: Option<&'a str>

description: Option<&'a str>

schedule_date: Option<DateTime<Utc>>

schedule_end: Option<DateTime<Utc>>

duration: Option<Decimal>

owner_user_id: Option<Uuid>

user_id: Option<Uuid>

asset_id: Option<Uuid>

priority: Option<&'a str>

maintenance_type: Option<&'a str>

recurring: Option<bool>

repeat_interval: Option<i32>

repeat_unit: Option<&'a str>

repeat_type: Option<&'a str>

repeat_until: Option<NaiveDate>

Implementations

impl<'a> RequestFieldUpdates<'a>

pub fn is_empty(&self) -> bool

True when no field is set — callers can skip the UPDATE entirely.