#28949: Multibyte table name or column name causes miscalculation of the length
of
index name.
-------------------------------------+-------------------------------------
Reporter: Pak Youngrok | Owner: Jacob
| Walls
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Normal | Resolution: wontfix
Keywords: migration multibyte | Triage Stage:
index | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
Closing per [https://github.com/django/django/pull/15273 discussion]. We
cannot use `encode()` because identifier limits are express in chars not
bytes, chars that can have 2, 3, 4 bytes. It may also depend on encoding
of the operating system or database, so it's not feasible to prepare a
fully backward compatible solution. I'd say that if you decided to use
non-ASCII chars in identifiers, you actually did this to yourself. Any
solution would be error-prone.
--
Ticket URL: <https://code.djangoproject.com/ticket/28949#comment:10>
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/066.776fccef3e2c06885ea3434ae54e1293%40djangoproject.com.
