Comments on: Denormalizing Model Abstraction in Django http://www.davidcramer.net/code/402/denormalizing-model-abstraction-in-django.html A blog about Django, JavaScript, CSS, and general web development. Fri, 12 Mar 2010 19:46:01 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: Thierry Schellenbach http://www.davidcramer.net/code/402/denormalizing-model-abstraction-in-django.html/comment-page-1#comment-20598 Thierry Schellenbach Fri, 02 Jan 2009 23:07:42 +0000 http://www.davidcramer.net/?p=402#comment-20598 Well we actually use Sql alchemy, which makes it very easy to achieve. Running two orms is sometimes annoying overhead though. Well we actually use Sql alchemy, which makes it very easy to achieve. Running two orms is sometimes annoying overhead though.

]]> By: Doug Hellmann http://www.davidcramer.net/code/402/denormalizing-model-abstraction-in-django.html/comment-page-1#comment-20592 Doug Hellmann Wed, 31 Dec 2008 00:10:14 +0000 http://www.davidcramer.net/?p=402#comment-20592 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. 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.

]]> By: Jj http://www.davidcramer.net/code/402/denormalizing-model-abstraction-in-django.html/comment-page-1#comment-20591 Jj Tue, 30 Dec 2008 23:46:13 +0000 http://www.davidcramer.net/?p=402#comment-20591 This is too powerful to fall on untrained hands... I agree about the TemplateModel, it made me think of Django Templates This is too powerful to fall on untrained hands…

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

]]> By: Rock Howard http://www.davidcramer.net/code/402/denormalizing-model-abstraction-in-django.html/comment-page-1#comment-20590 Rock Howard Tue, 30 Dec 2008 12:12:10 +0000 http://www.davidcramer.net/?p=402#comment-20590 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. 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.

]]>