#11487: Oracle encoding bug when saving more than 4000 characters
-------------------------------------+-------------------------------------
Reporter: mdpetry | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle database | Triage Stage: Accepted
nclob clob |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by RohitV24):
We are currently experiencing the same issue while inserting large strings
(between size 2000-4000 characters) into the Oracle database.The
NLS_NCHAR_CHARACTERSET on our database is AL16UTF16 which assigns 2 bytes
for a char .From digging in a little deeper, it looks like a string is
mapped to cx_Oracle.STRING which is then mapped to either a VARCHAR,
NVARCHAR or LONG in Oracle and the conversion to long in case of long
values is causing the error. It looks like the issue with 4000 characters
was fixed by setting the input size to cx_Oracle.CLOB when it reached the
character limit. Using 2000( for utf-16) seems to work fine and solve the
problem. Would setting the comparison value to 1000 (taking into
consideration other encoding formats) before setting it to CLOB be the fix
for this issue?
--
Ticket URL: <https://code.djangoproject.com/ticket/11487#comment:39>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.b89b51fc047d22dabf54331700af6792%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
