#33671: Migrations crashes when adding/altering collations on indexed columns on
Oracle.
----------------------------------+----------------------------------------
Reporter: Mariusz Felisiak | Owner: Mahesh Gupta
Type: Bug | Status: assigned
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: oracle collation | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------+----------------------------------------
Comment (by Mahesh Gupta):
As per https://docs.oracle.com/en/error-help/db/ora-43923/ Collation are
divided into groups and
Group 1: BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS,
USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS
Group 2: BINARY_CI, USING_NLS_SORT_CI, and USING_NLS_SORT_VAR1_CI
Group 3: BINARY_AI, USING_NLS_SORT_AI, and USING_NLS_SORT_VAR1_AI
and action suggested by Oracle is
When modifying the column collation, specify a new collation that is in
the same group as the current column collation. If there is no current
collation, because you changed the column data type at the same time and
the old data type is not a character data type, then select a collation
from Group 1 as the new collation.
Reading this, should we really fix this or this is more of a user error
and they should act accordingly?
--
Ticket URL: <https://code.djangoproject.com/ticket/33671#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/0107018ebf5d627e-bb4ebf2c-623d-4279-afce-72e8044f51f8-000000%40eu-central-1.amazonses.com.
