Closed jredrejo closed 1 year ago
Is this an issue with the old table not being dropped, or rather with the index being created when it already exists?
Is this an issue with the old table not being dropped, or rather with the index being created when it already exists?
The old table is not dropped, thus the index exists when it's being created, causing the error.
Observed behavior
After #9292 , the schedulerjobs table is not in use anymore, but there's no migration to remove it from the database. This is causing migration problems in Postgresql, and Kolibri can not start anymore.
Errors and logs
Expected behavior
Starting kolibri should drop current scheduledjobs table (and its indexes) so migrations can happen
User-facing consequences
kolibri won't start after upgrading to 0.16.x if Postgresql is used
Steps to reproduce