Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the Backend for Mass Record Deletion #5169

Closed
Tracked by #4397
Bonapara opened this issue Apr 25, 2024 · 2 comments · Fixed by #5320
Closed
Tracked by #4397

Improve the Backend for Mass Record Deletion #5169

Bonapara opened this issue Apr 25, 2024 · 2 comments · Fixed by #5320
Assignees
Labels
scope: backend Issues that are affecting the backend side only size: short

Comments

@Bonapara
Copy link
Member

Current Behavior

pg_graphql constraints restrict deletion to a maximum of 30 records per operation.

Desired Behavior

Implement a loop on the delete request to delete more records in a single operation.

@pacyL2K19
Copy link
Contributor

I can work on this @Bonapara
cc: @FelixMalfait

@FelixMalfait
Copy link
Member

Thanks @pacyL2K19 I think the master issue which includes this was taken by @gitstart-twenty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: backend Issues that are affecting the backend side only size: short
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants
@FelixMalfait @Bonapara @lucasbordeau @pacyL2K19 and others