Code review comment for lp:~free.ekanayaka/storm/infoheritance

Okay, thanks for explaining, I'm heading off for the day but will check the old revisions tomorrow. Not sure if it makes any difference, and maybe it goes without saying, but note that the branch implements exactly the infoheritance approach, where you have a separate "child" class referenced by the parent and holding extra information, and does *not* introduce polymorphism at the class-hierarchy level (the OOP-style), which is for instance the way this implemented in SQLAlchemy. So in practice I'd say it doesn't introduce further abstractions with respect to the infohertiance approach.