Context Navigation

SingleInstance

-              v14
+              v15
 That means writing Model(kwargs) would always return a fresh instance and bypass the instance. Since Django's ORM would use the API internally, doing Model.objects.get would (by default, overridable in the manager) return the singleton. The default related manager would also have a new get_from_db method to force retrieving and instantiating from the DB only.
 == Proposal #2 (The Original Proposal) ==
+== (The Original Proposal) ==
 This would always be enabled. You cannot turn it off. If stuff is broken by having this on then it should be broken.
 This can cause problems with serializers, and things that modify querysets and shouldn't (e.g. .extra). That is the only reason it should be turned off. If those problems are addressed there is no reason to use #17 and to have it enabled 100% of the time.
 A simple workaround querysets, and this would branch into being able to store .values() as partials as well (this code is untested, but should give a general idea):
+A simple workaround for querysets issues, and this would branch into being able to store .values() as partials as well (this code is untested, but should give a general idea):
 {{{
 …
 (The code above is taken from an unpublished update to the django-sphinx package.)
+As for serializers, these should probably bypass the instance caching, as they can have stale data available, better solutions are up to you.