Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Index create is in both the migration and the initial sql file. #72

Open
JeremyMahieu opened this issue Sep 21, 2024 · 0 comments
Open

Comments

@JeremyMahieu
Copy link
Contributor

          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.

Originally posted by @JeremyMahieu in #71 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant