post_init signal or overriding __init__ which is the way to go

2011-02-20 Thread Christan
By another post I simultaneously posted with this one, Now, I confirmed myself that instance of Foo that gets associated with model instance will not be saved in db, because it's not a subclass of one of the fields that model provides. *Now, only thing remaining is, whether I use post_init

Re: What will happen when a model I modified get saved.

2011-02-20 Thread Christan
1) That was a typo, forget it. 2) This answers my question, Thanks :) 3) I know this, but haven't tried South yet. BTW., Thank you for your time > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to

What will happen when a model I modified get saved.

2011-02-20 Thread Christan
See the model below, class Foo(models.Model): x = model.IntegerField() Also, a class as follows class Bar(Object): y = 1212121L - Now, If I modified above Foo like this class Foo(models.Model):

Populating extra fields on models at init that doesn't have to be saved in table and originally isn't part of the model.

2011-02-20 Thread Christan
I've this model class DistributionList(CommonList): distributionListID = models.IntegerField() NB: CommonList is another model with abstract=True in Meta class. (Abstract Base Class) Now, On the initialization of this DistributionList(whether newly created or retrieved from db), I've to