Joseph Kocherhans wrote:
On 12/27/05, Dody Suria Wijaya <[EMAIL PROTECTED]> wrote:
2. why create a "virtual" module at runtime for each model (the
plural+lowercase of model class name)?
I suppose binding the methods (get_XXX) to the model's class (class
method) is more easily understood, and can be implemented in terms of an
inheritance/mixin. That way, I could hold on to 1 thing to do everything
with the model.
This is currently being fixed in the magic-removal branch. There are a
few recent threads on the django-dev mailing list discussing the
changes.
I just visited http://code.djangoproject.com/wiki/RemovingTheMagic
awesome, seems to answer most of my questions on django model.
One more thing that I have not seen is overrideable "prepare new row"
method. triggered to provide customized field value, just after model
instance creation. ie:
from django.db import models
class Person(models.Model):
first_name = models.CharField(maxlength=30)
last_name = models.CharField(maxlength=30)
def prepare(self):
self.first_name = 'anonymous at %s' %
datetime.date.today().isoformat()
this commonly used to provide user filling a new form with a feedback on
what the default value would be if they choose not to fill/modify that
field before saving the form.
--
dsw
