Fix db structure summary timestamp - #20423
Open
M393 wants to merge 1 commit into
Open
Conversation
This should be the max timestamp, instead it was the min. Signed-off-by: Maximilian Krög <maximilian.kroeg@geocept.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## QA_5_2 #20423 +/- ##
============================================
- Coverage 50.55% 50.54% -0.01%
Complexity 17244 17244
============================================
Files 607 607
Lines 68783 68783
============================================
- Hits 34773 34768 -5
- Misses 34010 34015 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
In Database -> Structure
Creation,Last update, andLast checkall showed the min timestamp of any table in theSumrow.Last updateshould display the highest instead.Not so sure if the other two columns should continue to display the min or max timestamp.
The other two timestamps are calculate just above and below the changed code for the max update timestamp.
Enable in
config.inc.php: