On Mon, 2008-11-17 at 12:49 +0100, Marco Minutoli wrote: > I have this model: > > class Ticket(models.Model): > ## ForeignKey > project = models.ForeignKey ( > 'Project', > null=True, > blank=True, > verbose_name="Project", > ) > submitter = models.ForeignKey ( > User, > related_name="submitter", > verbose_name="Submitter", > ) > assigned_to = models.ManyToManyField ( > User, > blank=True, > null=True, > verbose_name="Assigned to", > ) > > > I would like to send an email to all 'assigned_to' when a ticket is > created. So i've override the Ticket Model's save method: > > def save(self): > super(Ticket, self).save() > print self.assigned_to.all() > print self.submitter.username > > But the "self.assigned_to.all()" is always empty, whilst > self.submitter.username is correct.
Because something cannot be included as part of a many-to-many relation until is has a primary key value -- which means it has to be saved first. So the new Ticket instance must be saved and *then* the many-to-many saving happens. That is, after Ticket.save() has returned. At some point in the future we'll most likely add a signal that you can use to process things when a many-to-many is updated, but at the moment, the way to do this is to manually trigger the emailing wherever the many-to-many is updated (in your view code). It's not a perfect solution, but it works. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
