<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mutation on Washington Botelho</title><link>http://www.wbotelhos.com/tags/mutation/</link><description>Recent content in mutation on Washington Botelho</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 08 Aug 2021 00:00:00 -0300</lastBuildDate><atom:link href="http://www.wbotelhos.com/tags/mutation/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL with Absinthe on Phoenix - Mutation</title><link>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-mutation/</link><pubDate>Sun, 08 Aug 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-mutation/</guid><description>Updated at: Jul 23, 2023 In the last article about GraphQL, we learned how to create a Query and how to avoid N + 1. The systems need to fetch data but the most of time we need to create these data too and GraphQL has a mechanism called Mutation to do this job.
Goal Create a Mutation to save a book using the code of the last article
Mutation The Mutation works very similar to Query, it queries the data in the same way, but after creating the record, and as expected we receive the input data as a parameter, like in Query, but instead it be used as a filter it&amp;rsquo;s used as a parameter to be inserted into the database.</description></item></channel></rss>