You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that index is in both the migration and the initial sql file. This is not ok, not your fault.
You can temporarily fix it by editing the migration history table yourself and add "20240405204318_TransactionsIndex" version "8.0.3". Then it won't try to do the migration again and start up propertly.
@dallmann-consulting you can't update the SQL-Server/Create_OCPP.Core.sql after the migration has already been created. Leave it as it is and create new migrations instead of modifying the initial database creation file.
Or delete the migrations after you recreate the .sql file. But this isn't foolproof either. The whole point is people can get new database updates after already having a working install without needing to delete their database.
You can temporarily fix it by editing the migration history table yourself and add "20240405204318_TransactionsIndex" version "8.0.3". Then it won't try to do the migration again and start up propertly.
@dallmann-consulting you can't update the
SQL-Server/Create_OCPP.Core.sql
after the migration has already been created. Leave it as it is and create new migrations instead of modifying the initial database creation file.Or delete the migrations after you recreate the .sql file. But this isn't foolproof either. The whole point is people can get new database updates after already having a working install without needing to delete their database.
Originally posted by @JeremyMahieu in #71 (comment)
The text was updated successfully, but these errors were encountered: