#34219: Collation is not preserved when field is altered on PostgreSQL and
MySQL.
-------------------------------------+-------------------------------------
Reporter: David Foster | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ae0899be0d787fbfc5f5ab2b18c5a8219d822d2b" ae0899b]:
{{{
#!CommitTicketReference repository=""
revision="ae0899be0d787fbfc5f5ab2b18c5a8219d822d2b"
Fixed #34219 -- Preserved Char/TextField.db_collation when altering column
type.
This moves setting a database collation to the column type alteration
as both must be set at the same time.
This should also avoid another layer of the column type alteration when
adding database comments support (#18468).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34219#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/010701853876b652-f3fe4af8-88af-40d5-b71f-6fc153e8d39e-000000%40eu-central-1.amazonses.com.
