#36675: Oracle dialect depends on implementation detail which was changed in
python-oracledb 3.4
-------------------------------------+-------------------------------------
Reporter: Anthony Tuininga | Owner: Varun
| Kasyap Pentamaraju
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Varun Kasyap Pentamaraju):
I've examined the code in the stable/5.2.x branch and found that all three
changes mentioned in the ticket are already implemented:
1. In django/db/backends/oracle/base.py: Already using `bytes` instead of
`Database.Binary`
2. In django/db/backends/oracle/operations.py: Already using
`datetime.datetime` instead of `Database.Timestamp`
3. In django/db/backends/oracle/utils.py: Already using `datetime.date`
instead of `Database.Date`
Could you please advise if there are other aspects of this ticket that
still need to be addressed, or if it can be closed as already fixed?
--
Ticket URL: <https://code.djangoproject.com/ticket/36675#comment:3>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a068590ed-db2e1db3-db56-4ed4-8a89-edeecb8442d0-000000%40eu-central-1.amazonses.com.
