interesting. I don't have a deep enough understanding of the internals. But would be neat to have a REPLACE_UNSAFE insert mode that catered to the backfill use case. I can track the status of relations inserted into spicedb during an initial bootstrap/backfill phase of integration in a separate datasource, but it would simplify the use case of idempotently re-running backfill operations if such a REPLACE_UNSAFE mode were available. In my case, TOUCH is not performant, possibly because of my complex schema, haven't dig into why. The

SELECT

transactions wreck a medium sized MySQL instance. Thx for the context!