$table
$table : string
What replacing one table's contents would actually leave behind.
The number this exists for is the comparison between the rows the table holds now and the rows Strata captured for it. Those two are equal on a table whose whole life was captured and unequal on a table that predates capture, and the difference is how many rows a restore would silently delete.
A confirm form that printed "restore 4,120 rows" without printing "the table currently holds 51,880" would be describing the same operation in a way that hides its cost. So both numbers are here, and the plan carries the warning rather than leaving the caller to work it out.
__construct(string $table, string $target, int $liveRows = 0, int $capturedRows = 0, list$columns = [], int $unreadable = 0, string|null $refused = null, float $seconds = 0.0) : mixed
Constructs a plan.
| string | $table | The table. |
| string | $target | Commit id the restore targets. |
| int | $liveRows | Rows the table holds now. |
| int | $capturedRows | Rows Strata captured for it at the target. |
| list |
$columns | The union of columns those rows carry. |
| int | $unreadable | Captured rows that could not be replayed completely. |
| string|null | $refused | Why the plan cannot proceed at all, or NULL. |
| float | $seconds | How long planning took. |
asRestorePlan() : \Drupal\strata\Restore\RestorePlan
The same plan in the shape the audit log records.
The audit table is shared with logical restores, so a physical plan presents itself as one subject - the table - with the coverage carried in the detail.
The plan.