Upsert behavior with composite tuple key

Hi @jacob thank you for bringing this issue to our attention. We have identified an issue with the treatment of :false in tuples and are working on a fix to address the issue in an upcoming release. I’ll be sure to update this post when I have more details.

Regarding upsert behavior, I’ll barrow from my response on thread 1072:

If you want upsert you must specify the unique key. You can alway use the actual entity id, in that case, you would not need to use any identity to perform an update. If you do want to identify an entity by a unique key, you must indeed specify that unique key (not its constituents). This is clean and unambiguous. We are looking at updating our docs to make this clear.

3 Likes