#18465: Date and Timestamp formats for Oracle Backend incorrect with Oracle RAC
11g
R2
-------------------------------------+-------------------------------------
Reporter: josh.smeaton@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
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 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Unreviewed => Accepted
Comment:
Marking accepted as the above description seems well-researched. I haven't
tried to reproduce this myself.
This can be patched in 1.4 and trunk. 1.3 is in security fixes only mode.
1.4 is actually questionable, the list of things to fix is:
{{{
Security issues.
Data-loss bugs.
Crashing bugs.
Major functionality bugs in newly-introduced features.
}}}
It is not entirely clear to me if this falls into any of those categories
(FWIW I think patching this should be done - this seems like a low-risk
fix).
A test case for this would be great. If you can add it to
tests/regressionstests/backends/tests.py in the pull request it will
reduce the amount of work needed on my end, but attaching a breaking query
here in a comment will be enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/18465#comment:2>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
