David Cramer's Blog - Latest Comments in Denormalizing Model Abstraction in Django

Re: Denormalizing Model Abstraction in Django

Thierry Schellenbach — Fri, 02 Jan 2009 18:07:42 -0000

Well we actually use Sql alchemy, which makes it very easy to achieve. Running two orms is sometimes annoying overhead though.

Re: Denormalizing Model Abstraction in Django

Doug Hellmann — Tue, 30 Dec 2008 19:10:14 -0000

We solved a similar problem using actual plugins and then delegating method implementations instead of trying to get fancy with subclasses. The primary class has core behaviors and knows how to find a plugin based on a name. The plugin is a separate object, instantiated by the primary class and invoked as part of the implementation of certain methods.

Re: Denormalizing Model Abstraction in Django

Jj — Tue, 30 Dec 2008 18:46:13 -0000

This is too powerful to fall on untrained hands...

I agree about the TemplateModel, it made me think of Django Templates

Re: Denormalizing Model Abstraction in Django

Rock Howard — Tue, 30 Dec 2008 07:12:10 -0000

This an interesting way to solve this problem, but I balk at the use of the term "denormalization" to describe what is going on. That word sets up expectations about the problem we are trying to solve that is at odds with what this mechanism actually provides.

I am searching for a better word and the closest I have come up with so far is "thunking" as the mechanism is akin to actualizing virtual function calling properties for Django models. (Also the implementation mechanism is sufficiently low-level to deserve the "thunking" label.) But I will bet that someone can suggest an even better name for this particular mechanism. Ideally it would be a fairly unique name so that searches can find it easily.

I am also looking forward to seeing if some other Django expert can suggest a cleaner and simpler way to implement a solution for this particular use case that offers the same power and flexibility. I wouldn't be surprised if the answer is no.

One final note - I also balk a bit at the use of the term TemplateModel as that term overloads the word Template in the Django context. I suggest ExtensibleBaseModel instead.