#7732: Oracle Backend with SessionPool
-------------------------------------+-------------------------------------
Reporter: halturin | Owner: mboersma
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: yandex-sprint | Needs documentation: 1
oracle session pool | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
It seems that allowing the use of the cx_Oracle inbuilt pooler is a good
idea.
As for the implementation: is the use of class level pool variable really
safe? It seems the pool instance is connection settings dependent, so
having just one pool per project seems suspicious.
Also, the close() implementation should probably do a rollback before
releasing the connection back to the pool.
--
Ticket URL: <https://code.djangoproject.com/ticket/7732#comment:14>
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.
