# AZ616: An older command, a newer database

The database (or the lock file) was last written by a newer version of rowstile than this command. Going on would put this older version's functions back, with everything fixed since undone, and a migration written now would be that step back, though it would read like an upgrade. An old global install, a CI image pinned to an older version or one machine that wasn't upgraded are the usual causes: upgrade the command there. To go back to the older version on purpose, add `--downgrade` (`rowstile apply`, `push`, `migrate` and `remove` take it). Development builds of the same version can't be told apart, and are never refused. A question to such a database (`rowstile can`, `explain-rule`, ...) that calls a function the newer version doesn't make, or makes with other arguments, stops with this code too: upgrade the command.

Reported by the command, against a database.
