feat(collection): repair SQL query slicing for content larger than 200Kb #3131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
closes #3129
β Type of change
π Description
When running the depoyment of nuxt-content database on D1 on kestra.io we noticed some weird values in the database:
Before this PR, the system allowed for queries up to 200Kb to be split in 2.
A query of 300Kb would have also be split in 2 (150 + 150) and fail.
In this PR, the system will run as many updates as needed.
π Checklist