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.

Sign up for GitHub

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

Jump to bottom

Test against mysql #46

Open
vegu opened this issue Jul 1, 2020 · 2 comments
Open

Test against mysql #46

vegu opened this issue Jul 1, 2020 · 2 comments
Labels
Minor Up to 4 hours
Milestone
4 Ready for Imple...

Comments

@vegu
Copy link
Contributor

vegu commented Jul 1, 2020

I think it'd be good to have tests run against mysql as well as sqlite so we can catch errors like #45
@vegu
Copy link
Contributor Author

vegu commented Jul 1, 2020

Should recreate the migrations that were dropped when we fixed #45 (all the verbose_name changes) and make sure mysql can handle those.

@vegu vegu mentioned this issue Jul 1, 2020
Open
@grizz
Copy link
Member

grizz commented Sep 4, 2020

Will be done as part of peeringdb/peeringdb#724

@grizz grizz added this to the 4 Ready for Implementation milestone Sep 4, 2020
@grizz grizz added the Minor Up to 4 hours label Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Minor Up to 4 hours
Projects
None yet
Milestone
4 Ready for Implementation
Development

No branches or pull requests
2 participants
@grizz @vegu