django-orm

class Toy(models.Model): name = models.CharField(max_length=20) desc = models.TextField() class Box(models.Model): name = models.CharField(max_length=20) proprietor = models.ForeignKey(User, related_name='User_Box') toys = models.ManyToManyField(Toy, blank=True) How to create a view that add Toy to Box? def add_this_toy_to_box(request, toy_id): K Z You can use Django's RelatedManager : A “related manager” is a manager used in a one-to-many or many-to-many related context. This happens in two cases: The “other side” of a ForeignKey relation. That is: class Reporter(models.Model): ... class

I have a website which fetches information from RSS feeds periodically (well, currently manually, and this is my problem). This is currently implemented as a normal Django view, which isn't very nice in my opinion. I'd like to have a Python program which is run using a cronjob instead of manually visiting the correct URL to update the information. What is the easiest way to make a Python program have access to my particular Django application and the Django ORM? from django.core.management import setup_environ from django.core.mail import EmailMultiAlternatives, send_mail from django.contrib

I need to get aggregated value of two columns. So first multiple them together and then get theirs sum() . Code below naturally does not work, it is just for clarification. Is it somehow possible or should I use raw SQL? SomeModel.objects .filter(**something) .aggregate(Sum('one_column' * 'another_col')) You don't need that much raw SQL using extra() . obj = SomeModel.objects.filter(**something).extra( select = {'total': 'SUM(one_column * another_column)'}, ) Antstud As I answered here https://stackoverflow.com/a/36024089/4614802 the correct solution depends on django version. For django < 1.8

An example Many-to-Many through relationship in Django: class First(models.Model): seconds = models.ManyToManyField(Second, through='Middle') class Middle(models.Model): first = models.ForeignKey(First) second = models.ForeignKey(Second) class Second(models.Model): Following the documentation on intermediary models , only one model of the pair to be related contains the ManytoManyField , model First in the example above. Is this correct? If so, which model should contain the ManytoManyField field? Are there any differences in using the relationship from either end depending on where the

I'm trying to do something that should be very common: add/edit a bunch of related models in a single form. For example: Visitor Details: Select destinations and activities: Miami [] - swimming [], clubbing [], sunbathing[] Cancun [] - swimming [], clubbing [], sunbathing[] My models are Visitor, Destination and Activity, with Visitor having a ManyToMany field into Destination through an intermediary model, VisitorDestination, which has the details of the activities to be done on the destination (in itself a ManyToMany field into Activity). Visitor ---->(M2M though VisitorDestination) --------

Consider the following skeleton of a models.py for a space conquest game: class Fleet(models.Model): game = models.ForeignKey(Game, related_name='planet_set') owner = models.ForeignKey(User, related_name='planet_set', null=True, blank=True) home = models.ForeignKey(Planet, related_name='departing_fleet_set') dest = models.ForeignKey(Planet, related_name='arriving_fleet_set') ships = models.IntegerField() class Planet(models.Model): game = models.ForeignKey(Game, related_name='planet_set') owner = models.ForeignKey(User, related_name='planet_set', null=True, blank=True) name = models.CharField