#19198: Oracle specific failures -------------------------------------+------------------------------------- Reporter: akaariai | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: (models, ORM) | 1.5-alpha-1 Severity: Normal | Resolution: Keywords: oracle | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Description changed by akaariai:
Old description: > Two Oracle specific failures have been introduced lately: > - Inability to deal with "%" in table or other identifier names > (present in 1.5a1) > - Oracle not working correctly for select_related cases where the > related model is null but contains character fields (master only) > > The first of the failures happens because Oracle backend does querystr % > args formatting and if a table name contains '%' then the formatting will > fail. > > The second one happens because we check for if all fetched columns are > None then set related object to None in models/query.py when creating the > related objects. Due to a recent change we correctly convert the row > values in compiler.py for related select fields, too. This means that > None values will be converted to '' and the check in models/query.py > fails. > > Draft patches available from: > https://github.com/akaariai/django/compare/fix_oracle2 New description: Two Oracle specific failures have been introduced lately: - Inability to deal with "%" in table or other identifier names (present in 1.5a1) - Oracle not working correctly for select_related cases where the related model is null but contains character fields (master only) The first of the failures happens because Oracle backend does querystr % args formatting and if a table name contains '%' then the formatting will fail. The second one happens because we check for if all fetched columns are None then set related object to None in models/query.py when creating the related objects. Due to a recent change we correctly convert the row values in compiler.py for related select fields, too. This means that None values will be converted to "" and the check in models/query.py fails. Draft patches available from: https://github.com/akaariai/django/compare/fix_oracle2 -- -- Ticket URL: <https://code.djangoproject.com/ticket/19198#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 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.