this is the tracking issue for fixing those TOUCH semantics: https://github.com/authzed/spicedb/issues/901

Yes I've seen this issue, but for the time being should I be using CREATE?

TOUCH is idempotent, so if you're looking for idempotency then I would just use TOUCH, unless you have a demonstrated performance challenge

We do have a lot of performance metrics that we're trying to hit so I think in that case CREATE makes more sense right?

what datastore backend are you using?

Also, is there more information about the GC?

for cockroach, I don't think we need to do anything to "fix" idempotency performance

Yeah this question is mostly about Postgres

there will be some follow-on effect for checks as well because there are fewer overall relationship versions

Are there any documented tests for that which I can read? I'm more worried about the check query performance than the write tbh which is why I think it might make more sense to only use the CREATE not the TOUCH but it depends on the correlation between check latency and data in the DB

if you can use

CREATE

, by all means go for it! some use cases are really challenging to know ahead of time whether the relationship you're trying to create already exists, and if you're using

CREATE

that would return an error if the relationship exists.

Got it, thanks for the info!!

yes, that's correct