-- The cluster's settings: everything in server.yaml that is not one
-- machine's own (listeners, certificates, the store's address), as a YAML
-- document every control plane reads and follows. Each change is a new row,
-- so what was in force before is there to compare with and go back to, and
-- two edits made at once cannot both win: the second is refused for naming
-- a version that is no longer the newest.
CREATE TABLE cluster_settings (
  version    INTEGER PRIMARY KEY,
  body       TEXT NOT NULL,
  note       TEXT NOT NULL DEFAULT '',
  created_at INTEGER NOT NULL,
  created_by TEXT NOT NULL DEFAULT ''
);