#18465: Date and Timestamp formats for Oracle Backend incorrect with Oracle RAC 
11g
R2
-------------------------------------+-------------------------------------
     Reporter:  josh.smeaton@…       |                    Owner:  akaariai
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.4
  (models, ORM)                      |               Resolution:  fixed
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:  oracle backend NLS   |      Needs documentation:  0
  Date Format                        |  Patch needs improvement:  0
    Has patch:  1                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by akaariai):

 I will wait with the backporting, I couldn't reproduce the error on Oracle
 XE 11g here on my machine. I applied the patch as there doesn't seem to be
 any documentation what is supposed to happen when NLS_TERRITORY is set
 together with something it is supposed to override, and there is at least
 one report of this on Oracle 11g RAC. The cost is one more query on
 connection setup.

 If it turns out there are more users possibly hit by this, and that this
 doesn't cause any problems for current users, then I will backport. (Sorry
 if this is overcautious, I am still not comfortable deciding what should
 be backported, what not).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18465#comment:7>
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 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 https://groups.google.com/groups/opt_out.


Reply via email to