Queries are read only, so you need an additional way to “mutate” or change data.
- [Instructor] Today we'll be learning…how to work with mutations.…In this video,…we'll look at how to change our data inside of Graphene.…And we'll also learn how to build custom mutations.…So what are mutations exactly,…and how are they like queries?…Well the main difference is that queries…are meant to be read-only.…They can't really change data.…Whereas mutations were made specifically to change data.…Whenever you use a mutation in Graphene,…you use the mutation keyword before your first set…of curly braces.…
Whereas the queries, use the query keyword.…Mutations also pass their arguments in…through an arguments class.…Whereas queries pass in arguments…through resolver parameters.…One thing they do have in common,…is they both use an ObjectType to bind…the resolver names to the actual functions.…We've seen this in previous videos,…set up something like this.…Now that we have a pretty good idea of what mutations are,…let's look at some code.…You'll notice in our polls directory I've added a new file.…
- Extending class-based views
- Building a REST API
- Working with GraphQL
- Building a basic schema
- Optimizing your environment
- Working with Pipenv
- How Django handles testing
- Securing the Django admin
Skill Level Advanced
1. Advanced Class-Based Views
2. Building a REST API
Authentication with DRF6m 14s
3. GraphQL: An Alternative API
4. Optimizing Your Environment
5. Tests, Tests, Tests
6. Securing Django
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.