#20201: Oracle String Length Issue with CLOB and NCLOB
-------------------------------------+-------------------------------------
Reporter: deejross | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.5
(models, ORM) | Resolution: needsinfo
Severity: Release blocker | Triage Stage:
Keywords: oracle | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ikelly):
I can confirm that this bug is still around. The backend marks strings
that are longer than 4000 characters as a CLOB when sending them to the
database. The problem is that the limit is actually 4000 ''bytes'', not
4000 chars. Consequently, as a practical matter the limit depends on the
particular national character set used by the database, and for a
variable-length encoding the particular characters used in the string
would matter also. The only way I can see to generally fix it is to
(expensively) test-encode the string just to determine its length before
sending it. More practically, we should probably change the threshold
from 4000 to 1000 characters.
--
Ticket URL: <https://code.djangoproject.com/ticket/20201#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].
For more options, visit https://groups.google.com/groups/opt_out.
