#31592: Can't revert to Django 3.0.6 after running migration for 3.1a1
-----------------------------------------+------------------------
Reporter: אורי | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I upgraded to Django 3.1a1 and ran migrations. I also created my own
migration because of the change from `from django.contrib.postgres.fields
import JSONField` to `from django.db.models import JSONField`. My own
migration was generated automatically:
{{{
# Generated by Django 3.1a1 on 2020-05-14 16:25
from django.db import migrations, models
import speedy.match.accounts.models
class Migration(migrations.Migration):
dependencies = [
('match_accounts', '0006_auto_20200121_1731'),
]
operations = [
migrations.AlterField(
model_name='siteprofile',
name='diet_match',
field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.diet_match_default,
verbose_name='Diet match'),
),
migrations.AlterField(
model_name='siteprofile',
name='relationship_status_match',
field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.relationship_status_match_default,
verbose_name='Relationship status match'),
),
migrations.AlterField(
model_name='siteprofile',
name='smoking_status_match',
field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.smoking_status_match_default,
verbose_name='Smoking status match'),
),
]
}}}
Most of the things worked with Django 3.1a1 except a few things which I
will report later. But when trying to use Django 3.0.6 again, I ran the
following commands:
{{{
./manage_all_sites.sh migrate auth 0011
./manage_all_sites.sh migrate match_accounts 0006
}}}
Then, after running my websites with Django 3.0.6, I received an error
message:
`Incorrect padding`
I can't run my websites locally without deleting the database completely
including all users. I didn't find any way to fix the database to run it
with Django 3.0.6.
--
Ticket URL: <https://code.djangoproject.com/ticket/31592>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.dd6b5c6f132d3db7655b6606e582932d%40djangoproject.com.
