Context Navigation

Changes between Version 1 and Version 2 of Ticket #31221, comment 2

v1	v2
4	4	Yes, that was already in the installed apps when I encountered the problem.
5	5
6		When I debug the test program, it does appear to be running {{{register_type_handlers}}} as expected during database setup. It also seems to be performing the deserialization to a python dict when the fixtures are loaded (using ~~to_python)~~. I'm not sure what it's doing with the models after that though, since there's nothing in the test db during testing, and accessing model instance values from the queryset gives the hstore formatted strings.
	6	When I debug the test program, it does appear to be running {{{register_type_handlers}}} as expected during database setup. It also seems to be performing the deserialization to a python dict when the fixtures are loaded (using {{{to_python}}}) so at least it's aware of hstore. I'm not sure what it's doing with the models after that though, since there's nothing in the test db during testing, and accessing model instance values from the queryset gives the hstore formatted strings.
7	7	So the test data I gave above turns into: {{{[(4, 'First', ''), (5, 'Second', '"details"=>"this one isn\'t blank"')]}}}