Save vs Update in Django - Deepstash
Save vs Update in Django

Save vs Update in Django

Curated from: helmut.dev

Ideas, facts & insights covering these topics:

6 ideas

Β·

220 reads

2

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

Save

The ".save()" method is used to write a model instance to the database. It can be an existing record or even a new one. For an existing record, Django will run a SQL UPDATE statement on the database. For a new record, Django will run an INSERT.

2

128 reads

Problems with save()

When updating an existing record, Django will update every field. That means, if you changed only one field on the model instance, all the fields will be updated (with the values staying the same). This is inefficient, especially if the model has many fields.

Another problem is that if there's a significant amount of time in between the fetching of the record and the saving of it, it is possible that another request will have updated one of the fields on that record, and your model instance still has the old value.

Calling ".save()" now will overwrite the new value that someone else saved.

2

22 reads

Saving with update_fields

To prevent updating every field of the model you can use the update_fields parameter. It expects a list of fields that you want to save. The UPDATE that is run against the database then only updates those fields that you have specified.

For example, in case we only want to update the price of a toy, we would run "toy.save(update_fields=["price"])".

2

28 reads

When to use save

  • when creating a new record.
  • you have a model instance already, and you need to change some field values.
  • you've overridden the save() method to include some custom model logic.
  • you defined pre_save and post_save signals for that model.

2

15 reads

Update

The ".update()" method is available on each queryset object of the ORM. For example, "Toy.objects.filter(price__lt=50).update(price=50)".

This would update the price of all toys that are below a certain price. While this is for a range of records, it could also be used to update a single record: "Toy.objects.filter(name="hippo").update(price=120)".

2

13 reads

When to use update

  • you are updating fields of one or many records (note: update cannot be used to create a new record, like save can).
  • you don't need to re-use a model instance after updating.
  • you don't need your overridden save() method or any pre_save or post_save signals to run.
  • you know what your new field values must be without having retrieved the record(s).

2

14 reads

IDEAS CURATED BY

Mircea-Ioan Oprea's ideas are part of this journey:

Metaverse

Learn more about artificialintelligence with this collection

Find out the challenges it poses

Learn about the potential impact on society

Understanding the concept of Metaverse

Related collections

Similar ideas

Database indexes

7 ideas

Database indexes

en.wikipedia.org

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

β€”

100+ Learning Journeys

β€”

Access to 200,000+ ideas

β€”

Access to the mobile app

β€”

Unlimited idea saving

β€”

β€”

Unlimited history

β€”

β€”

Unlimited listening to ideas

β€”

β€”

Downloading & offline access

β€”

β€”

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates