Hi Shai, On 04/07/2017 06:02 AM, Shai Berger wrote: > This is an idea that came up during the djangocon-europe conference: Add the > ability to install general instrumentation hooks around the database > "execute" > and "executemany" calls. > > Such hooks would allow all sorts of interesting features. For one, they could > replace the current special-case allowing assertNumQueries & friends to > record > queries out of debug mode (it's an ugly hack, really), but they could also > support my imagined use case -- a context-manager which could prevent > database > access during execution of some code (I'm thinking mostly of using it around > "render()" calls and serialization, to make sure all database access is being > done in the view).
Another use-case is for preventing database access during tests unless specifically requested by the test (e.g. pytest-django does this, currently via monkeypatching). > My idea for implementation is to keep a thread-local stack of context- > managers, and have them wrap each call of "execute". We could actually even > use one such context-manager instead of the existing CursorDebugWrapper. Why a new thread-local instead of explicitly per-connection and stored on the connection? Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5d5ee8f1-6b22-c48c-7a6b-11eac2928b64%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
