You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should enforce horizon_minutes to be NOT NULL. This will require a data migration where we calculate the horizon based on the timestamp_utc of the forecast and the start_utc time of the forecast_value.
In theory yes but in practice this will require a corresponding migration for production environment where this is used. I don't have access to those anymore. Also I don't know if changing this is still relevant. @peterdudfield would know more!
Yea, we just need to write a script that would look at start_utc and created_utc and calculate the horizon minutes. I can always do that script, if @Chirag-01 you fancy doing the migration
We should enforce
horizon_minutes
to be NOT NULL. This will require a data migration where we calculate the horizon based on thetimestamp_utc
of theforecast
and thestart_utc
time of theforecast_value
.pv-site-datamodel/pvsite_datamodel/sqlmodels.py
Line 210 in 11080b3
The text was updated successfully, but these errors were encountered: