#11487: Oracle encoding bug when saving more than 4000 characters
---------------------------------------------------+------------------------
Reporter: mdpetry | Owner: nobody
Status: new | Milestone: 1.1
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: oracle
database
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ikelly):
* needs_tests: 1 => 0
Comment:
Thanks, rafax. I've actually tested with the same set of versions and not
reproduced the bug, so there must be something more to it. I suspect it
has something to do with the database encodings.
About the test case, it appears to be saving a string of exactly 4000
characters, not more than 4000 characters. Is that intentional? Also,
does it still replicate if you use an NCLOB column instead of a CLOB
column? Since that is the default for Django, that is what we should be
testing.
--
Ticket URL: <http://code.djangoproject.com/ticket/11487#comment:17>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
