Opened 12 years ago
Last modified 12 years ago
#19198 closed Bug
Oracle specific failures — at Initial Version
| Reported by: | Anssi Kääriäinen | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.5-alpha-1 |
| Severity: | Normal | Keywords: | oracle |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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
Note:
See TracTickets
for help on using tickets.