This repository has been archived by the owner on Nov 21, 2024. It is now read-only.
[ECO-1828] Fix volume calculations with cast to jsonb; facilitate concurrency #32
Conversation
This file contains 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
xbtmatt
changed the title
xbtmatt
force-pushed
the
ECO-1828
branch
2 times, most recently
from
678939c
to
847c64d
Compare
xbtmatt
pushed a commit
that referenced
this pull request
Jun 10, 2024
…#32) Undo format to see diff better
xbtmatt
force-pushed
the
ECO-1828
branch
4 times, most recently
from
650557f
to
eabf1e7
Compare
Undo format to see diff better
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
jsonbbefore using them. This is the column of the data field ultimatelyGET_DAILY_VOLUME()needs to be casted to jsonb:$1.volume_events::jsonbCREATE FUNCTION GET_DAILY_VOLUME=>CREATE OR REPLACE GET_DAILY_VOLUMEIF NOT EXISTS ... INSERTtoINSERT <initialize_volume_logic> ON CONFLICT ... DO NOTHINGto let the db handle concurrency. Same as the insertion we do withUPDATE_LATEST_STATE