Update Impacts Too Many Records

Seeing an

update impacts too many records

update impacts too many records

update impacts too many records

update impacts too many records when I try to trigger a mutation that changes multiple rows. I know I've got to be holding it wrong. What am I missing here? Both senderId and recipientId are definitely set correctly

mutation RequestAllTools($senderId: UUID!, $recipientId: UUID!) {
  updateToolsV2Collection(
    filter: { state: { eq: "ACTIVE" }, senderId: { eq: $senderId } }
    set: { state: "REQUESTED", recipientId: $recipientId }
  ) {
    __typename
  }
}

mutation RequestAllTools($senderId: UUID!, $recipientId: UUID!) {
  updateToolsV2Collection(
    filter: { state: { eq: "ACTIVE" }, senderId: { eq: $senderId } }
    set: { state: "REQUESTED", recipientId: $recipientId }
  ) {
    __typename
  }
}

mutation RequestAllTools($senderId: UUID!, $recipientId: UUID!) {
  updateToolsV2Collection(
    filter: { state: { eq: "ACTIVE" }, senderId: { eq: $senderId } }
    set: { state: "REQUESTED", recipientId: $recipientId }
  ) {
    __typename
  }
}

mutation RequestAllTools($senderId: UUID!, $recipientId: UUID!) {
  updateToolsV2Collection(
    filter: { state: { eq: "ACTIVE" }, senderId: { eq: $senderId } }
    set: { state: "REQUESTED", recipientId: $recipientId }
  ) {
    __typename
  }
}

jdgamble555•10/2/22, 6:28 AM

every single record with your filter is what should get impacted... is that not what is happening?

Kavanaugh LatiolaisOP•10/2/22, 5:02 PM

No the call errors out with “update impacts too many records” and nothing happens

garyaustin•10/2/22, 6:41 PM

I don't use graphql, but that error is from code looking at something called at_most_clauseat_most_clause. It seems to have a default value if not set, but in my quick scan of the source do not see where it gets set to a default. I think something called atMostatMost can be set in a "call".

jdgamble555•10/2/22, 7:33 PM

Here is the error - https://github.com/supabase/pg_graphql/blob/master/pg_graphql--0.4.0.sql#L3928... I suggest you post an issue - https://github.com/supabase/pg_graphql/issues

GitHub

Issues · supabase/pg_graphql

GraphQL support for PostgreSQL . Contribute to supabase/pg_graphql development by creating an account on GitHub.

GitHub

pg_graphql/pg_graphql--0.4.0.sql at master · supabase/pg_graphql

GraphQL support for PostgreSQL . Contribute to supabase/pg_graphql development by creating an account on GitHub.

Kavanaugh LatiolaisOP•10/2/22, 11:56 PM

Yeah that was next on my list assuming no one sees anything obviously wrong in the above

Update Impacts Too Many Records

Similar Threads

Similar Threads

Similar Threads