MySQL auto increment field

[ashokkumar88]

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review
• 1. The issue provides a reproduction available on
  Github,
  Stackblitz
  or
  CodeSandbox

---

Describe the bug

In MySQL handler the auto increment field is generated as Int! in the schema. In Mutation it is throwing error as it is a required field.

Field \"id\" of required type \"Int!\" was not provided."

Expected behavior

The autoincrement field should be of type ID!

Environment:

• OS: Windows
• @graphql-mesh/...:
• NodeJS:

Additional context

[ardatan]

The autoincrement field should be of type ID!

It is correct, MySQL handler creates fields with specific types like Int, Float or String.

In MySQL handler the auto increment field is generated as Int! in the schema. In Mutation it is throwing error as it is a required field.

I didn't understand the issue here. If you share a reproduction, we can help you better.

[ashokkumar88]

Here is an explanation about the issue.

I have a book table with following structure:

id (int) (not null) (primary key) (auto increment)
title (varchar)
category (varchar)

Then I called the following mutation:

mutation MyMutation($book: book_InsertInput = {category:"comics",title:"Book Title"}) {
  insert_book(book: $book) {
    id
  }
}

And it is throwing error that id field is required.

{
  "errors": [
    {
      "message": "Field \"book_InsertInput.id\" of required type \"Int!\" was not provided."
    },
    {
      "message": "Field \"book_InsertInput.id\" of required type \"Int!\" was not provided."
    }
  ]
}

As the id is a primary key and auto increment field, it is auto generated. We cannot pass it in the mutation.

The schema generated for book_InsertInput is also attached.