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

Sync fails with version 2.1 if backend is mysql #45

Closed
vegu opened this issue Jul 1, 2020 · 0 comments · Fixed by #47
Closed

Sync fails with version 2.1 if backend is mysql #45

vegu opened this issue Jul 1, 2020 · 0 comments · Fixed by #47
Labels
bug

Comments

@vegu
Copy link
Contributor

vegu commented Jul 1, 2020 •
edited
Loading 

    raise ValueError('The database backend does not accept 0 as a '
ValueError: The database backend does not accept 0 as a value for AutoField.

Appears to be an issue in migration 0007
@vegu vegu added the bug label Jul 1, 2020
@vegu vegu mentioned this issue Jul 1, 2020
Open
vegu added a commit that referenced this issue Jul 1, 2020
@vegu
empty these migrations because its only verbose_name changes, and pro…
8230d7f 
…ducing migration errors on foreignkey fields when running against mysql as backend (#45).
vegu added a commit that referenced this issue Jul 1, 2020
@vegu
The AlterField statements on some of these fields cause issues with m…
d517be8 
…igrating if running against mysql as backend (#45). Drop them for now and address this at a later point.
@grizz grizz mentioned this issue Jul 1, 2020
Merged
@grizz grizz closed this as completed in #47 Jul 1, 2020
grizz added a commit that referenced this issue Jul 1, 2020
@grizz @vegu
remove migrations (#47)
7ddb49f 
* add py3.7 tests and mark as supported version,
remove py3.4 tests and remove from support versions

* The AlterField statements on some of these fields cause issues with migrating if running against mysql as backend (#45). Drop them for now and address this at a later point.

Co-authored-by: Stefan Pratter <[email protected]>
@paravoid paravoid mentioned this issue Sep 25, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remove migrations peeringdb/django-peeringdb
1 participant
@vegu