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 7136,"when inheriting models, accessing related subclass instances can produce spurious relations depending on order",Andy MacKinlay,socrates,"If you are using the new multi-table inheritance feature, and have two or more subclasses (eg SubClassA and SubClassB) which inherits from a baseclass, and retrieve a base class instance `baseinstance` from the DB, the expected behaviour if `baseinstance` only has a corresponding SubClassA instance should be to throw a !DoesNotExist exception when accessing `baseinstance.subclassb`. However, if you have already accessed `baseinstance.subclassa`, `baseinstance.subclassb` will point to the corresponding SubClassA instance instead of raising the exception. The attached models.py includes a test case that documents this.",,closed,Core (Other),dev,,fixed,model inheritance,,Accepted,1,0,0,0,0,0