Update Impacts Too Many Records

Seeing an

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
  }
}

Supabase•4y ago•

5 replies

Kavanaugh Latiolais

Update Impacts Too Many Records

Seeing an

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
  }
}

Update Impacts Too Many Records

Similar Threads

Update Impacts Too Many Records

Similar Threads

Similar Threads

Similar Threads