#35655: Django crashes with Oracle database Version > 23.3 -------------------------------------+------------------------------------- Reporter: Suraj Shaw | Owner: Suraj | Shaw Type: Bug | Status: assigned Component: Database layer | Version: 5.1 (models, ORM) | Severity: Release blocker | Resolution: Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Comment (by Mariusz Felisiak):
As for me, it's an issue in Oracle not in Django itself. (2) and (3) are not doable (at least on this stage of our release cycle, (3) probably never, TBH). I'm not sure it's worth keeping 175b04942afaff978013db61495f3b39ea12989b for 23.3 > Oracle >= 23.0. Let's revert it, we can also close #35295 as "wontfix" (waiting for Oracle to make it work as promised). -- Ticket URL: <https://code.djangoproject.com/ticket/35655#comment:6> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107019112915f44-657ab275-e0b2-4b18-9630-cef7352eb364-000000%40eu-central-1.amazonses.com.