On Sun, Mar 10, 2013 at 2:15 PM, Petite Abeille <[email protected]> wrote: > > On Mar 10, 2013, at 8:28 PM, Aymeric Augustin > <[email protected]> wrote: > >> https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L548-L555 > > Last but not least… I couldn't help notice these suspicious looking operators: > > https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L479 > https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L495 > > E.g. TRANSLATE … USING NCHAR_CS… and LIKEC… > > I suspect these are some sort of workarounds some fundamental charset > encoding misunderstandings :) > > Perhaps best to revisit that in light of "Supporting Multilingual Databases > with Unicode" and "Programming with Unicode": > > http://docs.oracle.com/cd/E14072_01/server.112/e10729/ch6unicode.htm > http://docs.oracle.com/cd/E14072_01/server.112/e10729/ch7progrunicode.htm
These particular lookups have a long history of being tweaked due to users coming up with installations where the existing queries did not work. See tickets #5985, #11017 and #14149. I'd rather not reopen this issue unless the current implementation can documentably be shown to be broken. -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
