#34253: migrations don't apply
-------------------------------+--------------------------------------
Reporter: kamikaze | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 4.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by kamikaze):
Replying to [comment:1 Tim Graham]:
> You haven't stated what the unexpected behavior is. If the migration
doesn't execute any SQL (which is impossible to know given the information
you provided) then the output looks correct. For example, if you added
`default=1` to the field, then no SQL queries are expected.
I added initial `default=0` - table created, no default for column. then I
changed to `default=1` and alter didn't change anything as well. any idea
why? SQLAlchemy + alembic does such things.
--
Ticket URL: <https://code.djangoproject.com/ticket/34253#comment:3>
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/01070185a363ad6b-a6c3eba5-ebad-43d3-9e73-dd321c89d2ac-000000%40eu-central-1.amazonses.com.
