#20226: Django problematic when Oracle when column/table names are mixed case -------------------------------------+------------------------------------- Reporter: calcium | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.5 (models, ORM) | Resolution: Severity: Normal | Triage Stage: Keywords: Oracle, ORM | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 1 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by calcium):
* needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: Oops... the line above should read + m = map(str.isupper, str(field.column)) and not + m = map(str.isupper, field.column) -- Ticket URL: <https://code.djangoproject.com/ticket/20226#comment:1> 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. For more options, visit https://groups.google.com/groups/opt_out.