pub fn migrate(
context: &mut Context,
arguments: &Arguments,
) -> Result<Outcome, Failed>Expand description
migrate: brings a SQLite file, a running server, or a legacy index into
this engine.
The kind is defaulted from the source and not guessed at. The other
migration tool argues, correctly, that deciding which migration to run by
looking at the source would “pick wrongly exactly once, on somebody’s real
data” - but that argument is about a directory against a file, which are
both just paths and cannot be told apart. postgres://host/db is not a path
on any platform this runs on, so there is nothing here to be ambiguous
about, and the failure mode of getting it wrong is “there is no such file”
rather than a migration of the wrong thing. --kind still overrides it.