Troubles with upsert on composite tuples

[brandonbloom]

@jaret

I am confirming with the dev team, but I believe there was another issue with ref resolution that was only recently fixed.

I’ve upgraded to the latest and the behavior I’m seeing is the same as described in my original comment.

@jaret

Reviewing your example gist, it looks like you are asserting a value for the composite attribute. As the docs above indicate, you should not do that.

I originally tried to assert the individual elements, but that causes the problem described in this thread. In short, the transaction will fail with a conflict error. To quote you from over in that thread:

@jaret

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.

After reading that, I tried asserting the composite tuple key directly, which has the problems described in my original post.

@jaret

we do support :db.type/ref and I’ll add it to that page shortly.

Glad to hear this. Was concerned for a moment there, since using refs in composite keys is a critical use case for me!

If you’re saying all this stuff works: Could you please provide a repl log demonstrating how to upsert via a tupleAttrs based multi-attribute unique/identity key?

Thanks!