Table inside the schema, or '' for a schema/file-level outcome that isn't tied to one table
=> the down-swap uses this when it declines to overwrite an existing local .db (ES#8), since
that conflict is the whole file, not a single table within it.
rows actually moved (0 when skipped)
true when this target was left alone
OptionalreasonWhy it was skipped, when it was.
conflict the target already held data & the ConflictHandler declined (on the
down-swap this is a file-level decline, reported with table: '')resumed an earlier interrupted run already moved it, per the resume journal in the data dir
Per table outcome of a swap.