When the user runs IARA with an outdated database, it throws an error. The great advantage of having migrations is preventing this from happening. We cannot read the database by passing the migration path as an argument, because this is incompatible with read_only, which is necessary. The solution should be to apply the migrations before opening the database for reading.
When the user runs IARA with an outdated database, it throws an error. The great advantage of having migrations is preventing this from happening. We cannot read the database by passing the migration path as an argument, because this is incompatible with read_only, which is necessary. The solution should be to apply the migrations before opening the database for reading.