17 lines
1.2 KiB
SQL
17 lines
1.2 KiB
SQL
-- The tables of the delivery plans' machinery leave the store (novox/hq ADR 0539 §17, design 47 release 6, issue 1945).
|
|
--
|
|
-- A machine follows its wants and applies a module from the composition the controller writes for it (ADR 0539 §1, §2), so
|
|
-- the controller keeps no record of what it sent, no counter of the assignments a send was composed from, no verdict of a
|
|
-- gate that judged a build on its first machine and no measure of how long a plan's tier or a machine's apply took. This
|
|
-- drops the four tables that kept them: declaration_send (0094), assignment_generation (0094), build_gate (0073) and duration
|
|
-- (0066, 0075).
|
|
--
|
|
-- **It is one-way**: a controller older than this schema is refused by the put-back gate (the highest migration it carries is
|
|
-- recorded by its version, issue 352). What stays: the node row and its columns (the digest of the last send, which the old
|
|
-- reads of `status` still name until they go with their verbs), the bus step, the core box and the refused registrations.
|
|
-- The function raise_assignment_generation and its triggers went with 0105.
|
|
drop table if exists declaration_send;
|
|
drop table if exists assignment_generation;
|
|
drop table if exists build_gate;
|
|
drop table if exists duration;
|