#7732: Oracle Backend with SessionPool
---------------------------------------------------+------------------------
Reporter: halturin | Owner: mboersma
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
yandex-sprint oracle session pool
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Comment (by dberg...@juniper.net):
I've never looked at the test suite, nor do I have a clue how cx_oracle
manages connections and transactions, but perhaps problems arise because
some of the tests don't do a commit? The connection would then go back
into the pool with an open transaction, and when it was next pulled out of
the pool, the state in that connection would be different from what is
expected. In general, using any pooled resource can expose sloppy
practices in the calling code (failure to properly initialize shared
memory, db connection leaks, etc.).
--
Ticket URL: <http://code.djangoproject.com/ticket/7732#comment:11>
Django <http://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 this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
