#34253: migrations don't apply
-------------------------------+--------------------------------------
Reporter: Oleg Korsak | 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 Mariusz Felisiak):
> 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.
Django's ORM don't use defaults defined at the database level and always
specify the value when performing inserts instead. #470 is a ticket to
allow using database defaults.
--
Ticket URL: <https://code.djangoproject.com/ticket/34253#comment:4>
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/01070185a45c787a-21b14909-92a0-446c-a7cf-0f4832d31254-000000%40eu-central-1.amazonses.com.
