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
Stems from discussions with @calexh-sar - in the IRB prototype for example it would be nice for the top level key in a kkv data store to be study_123 - but how to atomically get the next id to use as the top level key before insertion of the record? If a new script was added that allowed for something like new_id = allocate_kkv_top_level_key("study_") then it could safely be done by using the id of the newly inserted row, which would contain minimal placeholder information. Exact syntax is not defined.
The text was updated successfully, but these errors were encountered:
Stems from discussions with @calexh-sar - in the IRB prototype for example it would be nice for the top level key in a kkv data store to be
study_123
- but how to atomically get the next id to use as the top level key before insertion of the record? If a new script was added that allowed for something likenew_id = allocate_kkv_top_level_key("study_")
then it could safely be done by using the id of the newly inserted row, which would contain minimal placeholder information. Exact syntax is not defined.The text was updated successfully, but these errors were encountered: