I see this ticket: Ticket #6510. What if they just used the function
from IfNode?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
Is there a reason not to have a signal before and after creating an
entry into a ManyToMany table. I have a piece of code i need to call
when this relationship is created. I don't know of any signal that
exists already, so I created my own. Thought it might be an
interesting feature to add,
I have revision 10865, and use postgresql. I've noticed that with
models like this:
class Edition(models.Model):
name = models.CharField(max_length=25)
class Email(models.Model)
edition = models.ForeignKey(Edition,null=True,blank=True)
If I delete an edition (edition.delete()), it deletes
Say I have a model like this:
class Photo(models.Model):
name = models.CharField(max_length=25)
user = models.ForeignKey(User,related_name='photos')
image = models.ImageField()
site = models.ForeignKey(Site,related_name='site_photos')
objects = CurrentSiteManager()
I've
== 'RelatedManger':
self.__filed_name =
self.model._default_manager.__field_name
else:
self.__field_name = field_name
self.__is_validated = False
On Jan 27, 5:09 pm, Stephen Sundell <stephen.sund...@gmail.com> wrote:
> If I creat
If I create a model such as this:
class Profile(models.Model):
user = models.ForeignKey('django.contrib.auth.User')
my_site = models.ForeignKey('django.contrib.sites.Site')
objects = CurrentSiteManager('my_site')
when I try to do the query:
user.profile_set.all()
where user is
