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 have methods to add stuff to the database that perform some integrity checks and use bulk operations --this is nice.
But for example, adding objects or relationships or parameters requires to know the object class id, whereas the application side usually just knows the object class name. So one has to insert object class first, query back the result, extract the id and then insert objects or parameters or whatever.
We would like that 'figuring out the id'-part to happen spinedatabase-api side.
In principle, some code developed Spine Toolbox side (import from excel feature) can be used as a starting point.
The text was updated successfully, but these errors were encountered:
In GitLab by @manuelma on Dec 13, 2018, 13:02
We have methods to add stuff to the database that perform some integrity checks and use bulk operations --this is nice.
But for example, adding objects or relationships or parameters requires to know the object class id, whereas the application side usually just knows the object class name. So one has to insert object class first, query back the result, extract the id and then insert objects or parameters or whatever.
We would like that 'figuring out the id'-part to happen spinedatabase-api side.
In principle, some code developed Spine Toolbox side (import from excel feature) can be used as a starting point.
The text was updated successfully, but these errors were encountered: