jcompagner wrote:then i guess what you need is a merge: (with the options we have now in 6)
write to db -> an option to only write new keys and there values, don't touch the rest.
read from db -> an option to only get the new values don't delete new keys that are in the workspace.
Hi Johan, that sounds great, but we need these functions a little bit more extended:
write to db -> an option to update existing keys and write new keys
read from db -> an option to update existing values and get the new values (don't delete new keys that are in the workspace)
You could make a case for this, it could be that we only need to have the second option
because then your workspace is completely up to date and you could then write it (but the question is then what to do with keys that don't exist in the workspace anymore, i guess those can be deleted)
Keys that don't exist in the workspace should never be deleted, because the messages table can contain custom keys that we do not have in the workspace, but use in other products (like our saas applications that run on same database).
I reopened case 381926 and added these options to it.