Files
OmniRoute/bin
diegosouzapw ca1389b2e3 feat(db): order migrations by the numeric value of their prefix
New migrations will be named YYYYMMDDHHMMSS_description.sql (UTC). As text,
"20261113120000" sorts before "235", so the runner would apply a timestamped
migration ahead of the legacy tables it depends on. getMigrationFiles(), the
applied-ledger reads and getMigrationStatus() now order versions with
compareMigrationVersions() (arbitrary-precision numeric prefix; namespaced
ee-NNN after the whole main set; anything else last). For the legacy set,
all three digits, the order is identical to the old text sort, so no existing
migration moves. Pending stays "not in the ledger", so a timestamped migration
that reaches a database after a later-dated one applies exactly once.

The doctor command lists pending migrations in the same numeric order.
2026-11-13 13:18:35 -03:00
..
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00