#28816: Silent data loss when decreasing the max_length of a CharField
----------------------------+---------------------------------------------
Reporter: Gavin Wahl | Owner: Hasan Ramezani
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"1378d665a1c85897d951f2ca9618b848fdbba2e7" 1378d665]:
{{{
#!CommitTicketReference repository=""
revision="1378d665a1c85897d951f2ca9618b848fdbba2e7"
Fixed #28816 -- Prevented silencing data loss when decreasing
CharField.max_length on PostgreSQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28816#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ae27f460704e4fe1123dc8789f3d6eea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
