#10566: Support cx_Oracle compiled with WITH_UNICODE
---------------------------------------------------+------------------------
Reporter: ikelly | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: oracle
unicode
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
This should be fairly routine, since we already do a bunch of conversions
more or less in one place and we can hook in there. The only potential
challenge is knowing when to do this. Is it detectable from querying
something in `cx_oracle`? Or do we need to add a `DATABASE_OPTIONS` key
for it so that the user can tell us?
--
Ticket URL: <http://code.djangoproject.com/ticket/10566#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
