id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
22873	Rename BaseDatabaseWrapper.use_debug_cursor to force_debug_cursor	john@…	anonymous	"In Django 1.6, the logic for using the CursorDebugWrapper was:

* If db.connection.use_debug_cursor is True, use it
* If db.connection.use_debug_cursor is None, defer to settings.DEBUG
* if db.connection.use_debug_cursor is False, don't use it.

This was changed in the fix for #20420.  Commit [127218b92bb8] changed the logic to:

* If db.connection.use_debug_cursor is True, use it
* If db.connection.use_debug_cursor is False or None, defer to settings.DEBUG

I am using a management command to load lots of data into the database, and I was setting use_debug_cursor to False to disable query logging before my lengthy import.  I'd rather not have to remember to set DEBUG=False every time I run a management command on my dev box.  I'd like the 1.6 trinary behavior, as well as the better queries_logged property introduced in [40bfd8561d016]"	Cleanup/optimization	closed	Database layer (models, ORM)	dev	Normal	fixed			Ready for checkin	1	0	0	0	1	0