#6064: Allow database connection initialization commands
---------------------------------------------------+------------------------
Reporter: jacob | Owner: floguy
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by mdh):
I just updated this patch to work with the current trunk, since it hadn't
been touched for a year and had gotten rather stale. I also fixed some
bugs that were causing `connection_created` signals to be sent on every
'''cursor'''-creation for some back ends, rather than only when a new
database connection has really been made.
Unfortunately, fixing that bug broke the test for sqlite3, since in-memory
sqlite3 databases (of the sort used by the tests) are never actually
closed, and thus cannot be reopened by the tests. So I've had to disable
the test altogether for sqlite3, unless someone can come up with a
definitely-safe way to open a second temporary database somehow without
clobbering the old one. Seems like more trouble than it's worth.
It occurs to me that a separate `cursor_created` signal might actually be
useful, especially if it were passed a reference to the new cursor, but,
well, one thing at a time.
--
Ticket URL: <http://code.djangoproject.com/ticket/6064#comment:16>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
