ChatGPT解决这个技术问题 Extra ChatGPT

How to select a record and update it, with a single queryset in Django?

How do I run an update and select statements on the same queryset rather than having to do two queries: - one to select the object - and one to update the object

The equivalent in SQL would be something like:

update my_table set field_1 = 'some value' where pk_field = some_value

A
Adolfo

Use the queryset object update method:

MyModel.objects.filter(pk=some_value).update(field1='some value')

Just a fair warning... if you use the update method like this then any signals attached to that model or other "code stuff" won't run against the objects. Just a pointer from someone who got burned :)
@learning well dude, it all depends on your scenario. The update method is great for mass updates, but it should set off a warning in your head when you use it that you need to review any signals attached to that object that might also need to be manually fired
Is it possible to access the current model instance in the update function? like MyModel.objects.filter(pk=some_value).update(field1=self.data)
@DipakChandranP You should ask a new question rather than putting comments on a six-year-old one. But F() expressions are probably want you want.
@DMactheDestroyer 9 years later, I finally understand your comment. stackoverflow.com/a/71688507/417899
S
Slipstream

Django database objects use the same save() method for creating and changing objects.

obj = Product.objects.get(pk=pk)
obj.name = "some_new_value"
obj.save()

How Django knows to UPDATE vs. INSERT If the object’s primary key attribute is set to a value that evaluates to True (i.e., a value other than None or the empty string), Django executes an UPDATE. If the object’s primary key attribute is not set or if the UPDATE didn’t update anything, Django executes an INSERT.

Ref.: https://docs.djangoproject.com/en/1.9/ref/models/instances/


P
Pransh Tiwari

This answer compares the above two approaches. If you want to update many objects in a single line, go for:

# Approach 1
MyModel.objects.filter(field1='Computer').update(field2='cool')

Otherwise you would have to iterate over the query set and update individual objects:

#Approach 2    
objects = MyModel.objects.filter(field1='Computer')
for obj in objects:
    obj.field2 = 'cool'
    obj.save()

Approach 1 is faster because, it makes only one database query, compared to approach 2 which makes 'n+1' database queries. (For n items in the query set) Fist approach makes one db query ie UPDATE, the second one makes two: SELECT and then UPDATE. The tradeoff is that, suppose you have any triggers, like updating updated_on or any such related fields, it will not be triggered on direct update ie approach 1. Approach 1 is used on a queryset, so it is possible to update multiple objects at once, not in the case of approach 2.


Regarding 1. - I think the query result gets cached on first call to query, hence there is actually still just a one call to DB.
R
Riyas Ac

1st method

MyTable.objects.filter(pk=some_value).update(field1='some value')

2nd Method

q = MyModel.objects.get(pk=some_value)
q.field1 = 'some value'
q.save()

3rd method

By using get_object_or_404

q = get_object_or_404(MyModel,pk=some_value)
q.field1 = 'some value'
q.save()

4th Method

if you required if pk=some_value exist then update it other wise create new one by using update_or_create.

MyModel.objects.update_or_create(pk=some_value,defaults={'field1':'some value'})

R
Roman-Stop RU aggression in UA

If you need to set the new value based on the old field value that is do something like:

update my_table set field_1 = field_1 + 1 where pk_field = some_value

use query expressions:

MyModel.objects.filter(pk=some_value).update(field1=F('field1') + 1)

This will execute update atomically that is using one update request to the database without reading it first.


J
Jamil Noyda

only in a case in serializer things, you can update in very simple way!

my_model_serializer = MyModelSerializer(
    instance=my_model, data=validated_data)
if my_model_serializer.is_valid():

    my_model_serializer.save()

only in a case in form things!

instance = get_object_or_404(MyModel, id=id)
form = MyForm(request.POST or None, instance=instance)
if form.is_valid():
    form.save()

I think serializers are from Djanog Rest Framework and not Django proper.
Yeah, however Django form is from Django Proper.
c
cyberfly

Accepted answer works great, but it comes with some unwanted side effect.

For example, you are using imageField, the update() will work and update others data, but not update your imageField data

class ProfileSetting(models.Model):

    first_name = models.CharField(blank=True)

    logo = models.ImageField(blank=True, null=True, upload_to="profile/logo/")

update_data = {
  "first_name": "john",
  "logo": request.FILES['logo'] # logo will not be properly update
}

ProfileSetting.objects.filter(pk=some_value).update(**update_data)

Here is some example with good explanation Django ImageField is not updating when update() method is used