Context Navigation

Changes between Initial Version and Version 1 of Ticket #3615, comment 34

initial	v1
29	29	Some tickets I've found that are related to this (some of them very tangentially): #14204, #15933, #16026, #8317.
30	30
31		Perhaps efforts in this ticket can be ~~put only on enhancing the situation of tests with MySQL (i.e. move back the new sql code checks in `check_constraints()`~~ and leaving the other backend alone for now?
	31	Perhaps efforts in this ticket can be focused only on enhancing the situation of tests with MySQL (i.e. move back the new sql code checks in `check_constraints()` to the `mysql` backend) and leaving the other backend alone for now?
32	32
33	33	Also, there is this thread about some efforts that go somewhat in the opposite direction: Avoid the overhead associated with fixture (re)loading (and if work on this ticket lands maybe also foreign key constraint checking) before _every_ test method when fixtures are something that essentially don't change. The DB used in such experiments is precisely MySQL: http://groups.google.com/group/django-developers/browse_thread/thread/65a36a8a5433144c/81bc4d2d4fd8b866