#20292: Django 1.5.1: ORA-01843: not a valid month -------------------------------------+------------------------------------- Reporter: CarstenF | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.5 (models, ORM) | Resolution: Severity: Normal | Triage Stage: Accepted Keywords: Oracle, cx_oracle, | Needs documentation: 0 unicode | Patch needs improvement: 0 Has patch: 0 | UI/UX: 0 Needs tests: 0 | Easy pickings: 0 | -------------------------------------+------------------------------------- Changes (by mcallister.sean@…):
* cc: mcallister.sean@… (added) Comment: The breaking change for me is the fix to ticket #19606 The detection of unicode capability of the backend is somewhat broken, and if I force usage of {{{ convert_unicode = force_bytes }}} around line 70 in db/backends/oracle/base.py the errors seems to go away. I can reproduce the problem using this model: {{{ from django.db import models class TS(models.Model): ts = models.DateTimeField() d = models.DateField() }}} And then creating some instances: {{{ from .models import TS from datetime import datetime n = datetime.now() d= n.date() TS(ts=n, d=d).save() TS(ts=n, d=d).save() }}} The above snippets works on django 1.5.1 and cx_Oracle 5.0.4, but breaks when upgrading to to 5.1.2 (I don't think Instant client version plays into this, I compiled cx oracle against 11.2 and 10.2.0.5, same behaviour). The first save actually works, but the the second raises the invalid month error. This behaviour seems similar to this SO question: http://stackoverflow.com/questions/15396241/cx-oracle-ora-01843-not-a -valid-month-with-unicode-parameter Perhaps #19606 needs re-opening? -- Ticket URL: <https://code.djangoproject.com/ticket/20292#comment:4> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.8bee6bca5ee5f4454a0305cc7fdb76f7%40djangoproject.com?hl=en. For more options, visit https://groups.google.com/groups/opt_out.