django-typed-models

> django-typed-models https://github.com/craigds/django-typed-models Interesting, never came across it. But I've got a Django GitHub library (not yet open source, because it's in a project I've been working with on and off) that does the same for managing GitHub's accounts. An Organization and User inherit the same properties and I downcast them based on their polymorphic type field.

> The final optimization would have been to write a language that would define game entities in terms of the game components they were subject to and automatically generate the single class that was union of all possible types and would be a "row" in the table django-typed-models https://github.com/craigds/django-typed-models > polymorphic django models using automatic type-field downcasting > The actual type of each object is stored in the database, and when the object is retrieved it is automatically cast to the correct model class ... > the common thread was that a hierarchical OO structure ended up adding a lot of unneeded complexity for games that hindered flexibility as requirements changed or different behaviors for in-game entities were added. So, in order to draw a bounding box for an ensemble of hierarchically/tree/graph-linked