Db: Fix current week timeframe end #246
Open
+4
−2
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
sukhwinder33445
force-pushed
the
fix-current-week-timeframe
branch
from
a22a39f
to
a67e5ed
Compare
raviks789
reviewed
Sep 24, 2024
| @@ -0,0 +1 @@ | |||
| UPDATE timeframe SET end = 'now' WHERE name = 'Current Week'; | |||
There was a problem hiding this comment.
Insert the upgrade version number of the script into reporting_schema table.
INSERT INTO reporting_schema (version, timestamp, success, reason)
VALUES ('1.1.0', unix_timestamp() * 1000, 'y', NULL);| @@ -0,0 +1 @@ | |||
| UPDATE timeframe SET end = 'now' WHERE name = 'Current Week'; | |||
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.
The end value for the preconfigured time frame
Current weekis set to the upcoming Sunday, which leads that the reports contain false positive (future) data. The end must be set tonow.