hasura / hasura/graphql-engine

Add support for `limit`, `offset`, and `order_by` to both update and delete mutations

Open
#9,997 2 comments 11 reactions 0 assignees View on GitHub
k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Is your proposal related to a problem?

I expect update and delete mutation work with the same arguments as select queries. But instead, only `where` parameter is supported. And `limit`, `offset`, and `order_by` are not supported. That makes me do separate select query and separate mutation.

### Describe the solution you'd like

Add support for `limit`, `offset`, and `order_by` to both update and delete mutations.

### Describe alternatives you've considered

None

Contributor guide

Open the contributing guide

Research direction

Start by locating the update and delete mutation entry points and comparing their supported arguments with select queries. Check the existing mutation and query tests, then verify that limit, offset, and order_by work for both mutation types alongside where, with coverage for the resulting affected records.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.