-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(db-*): support atomic array $push db updates #13453
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
Open
AlessioGr
wants to merge
21
commits into
main
Choose a base branch
from
feat/$push
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+776
−64
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
…This allows usage of $push with just one single db call
we should chat about this one with @DanRibbens |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds atomic
$push
support for array fields. It makes it possible to safely append new items to arrays, which is especially useful when running tasks in parallel (like job queues) where multiple processes might update the same record at the same time. By handling pushes atomically, we avoid race conditions and keep data consistent - especially on postgres, where the current implementation would nuke the entire array table before re-inserting every single array item.The feature works for both localized and unlocalized arrays, and supports pushing either single or multiple items at once.
This PR is a requirement for reliably running parallel tasks in the job queue - see #13452.
Alongside documenting
$push
, this PR also adds documentation for$inc
.Changes to updatedAt behavior
#13335 allows us to override the updatedAt property instead of the db always setting it to the current date.
However, we are not able to skip updating the updatedAt property completely. This means, usage of $push results in 2 postgres db calls:
This PR changes the behavior to only automatically set updatedAt if it's undefined. If you explicitly set it to
null
, this now allows you to skip the db adapter automatically setting updatedAt.Note
I would like to note that this does differ from the behavior of other fields being set to
null
.For other fields, setting them to
null
will cause the database to think we want to set it to null. In this PR, we created an exception for theupdatedAt
field, where setting it to null will simply skip it from the db update, neither setting it to the current date (this would be the behavior if it wasundefined
) nor setting it to null in the db.The alternative to this would be adding a new property like
disableTimestampUpdates
, but that would be more code to maintain and less simple.=> This allows us to use $push in just one single db call
Usage Examples
Pushing a single item to an array
Pushing a single item to a localized array
Pushing multiple items to an array
Pushing multiple items to a localized array