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
Currently, the primary keys in the id column have to be continuous to the already existing keys on the OEP. This results in users having to check existing keys first and locally changing their keys to be in sequence with the keys on the OEP. This is unneccesary workload in my opinion. I remenber, that in open_MODEX this was handled automatically. Thus, independet what primary key was given in the local csv, when appending the data to the OEP table, primary keys were updated with continuous id's.
The text was updated successfully, but these errors were encountered:
Not sure, whether this issue should be here or in oedatamodel-api
Problems
When uploading new data versions, it is not checked whether a data version already exists. The upload does not fail.
https://openenergy-platform.org/dataedit/view/model_draft/cm_sedos_pipline_test
Currently, the primary keys in the
id
column have to be continuous to the already existing keys on the OEP. This results in users having to check existing keys first and locally changing their keys to be in sequence with the keys on the OEP. This is unneccesary workload in my opinion. I remenber, that inopen_MODEX
this was handled automatically. Thus, independet what primary key was given in the local csv, when appending the data to the OEP table, primary keys were updated with continuous id's.The text was updated successfully, but these errors were encountered: