TransactionDetails data reduction with lag and lead and export to csv #1164
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
…eduction and firstArrivingMeterValueIfMultiple
changed sql-query, uses now lag and lead sql-functions, added CSV export of Transaction-Details
style checks
3 tasks
|
The flag firstArrivingMeterValueIfMultiple is removed at the master, so this PR seems obsolete! |
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.
Adding an export function of the transaction details to provide easy access to the data of the charging process.
The use of data reduction is optional. The reduction algorithm is changed from first/last ever appearance of equal values to first/last appearance of equal values behind each other.
May fix #1004