-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/dwh component #50
Conversation
…methods for getting data from database and also executing raw requests or calling stored procedures. Also, it provides high level of communication with the database by implementing contexts - plant, solcast and enercast - allowing us to communicate with the database without writing SQL queeries but just passing parameters if required. Also, unit tests are added aligned to the structure of the DWH component.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Great work!
tests/dwh/context/test_enercast.py
Outdated
{ | ||
"plantname": "CC-LL", | ||
"AssetName": "PredPV1", | ||
"AssetId": "86358efb-c076-4bca-a775-0a63ec92d8ba", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these be randomised a bit more? Seems very realistic and possibly a security issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thing: Since this is a public library I think we should stick to plant-names that are totally unrecognisable, like "SOMESITE" and "ANOTHERSITE".
No description provided.