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

Review and fix DB migrations #168

Open
decembrya opened this issue Jan 10, 2022 · 0 comments
Open

Review and fix DB migrations #168

decembrya opened this issue Jan 10, 2022 · 0 comments

Comments

@decembrya
Copy link

When starting a new instance of the app and DB from scratch the current migrations will not create an 'Alias' column in the parties table which causes the ResultsCrawler to fail.

Noticed that there are some commented out migrations even though the columns are used. Review and recreate migrations so that a new app setup will work out of the box.

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