well, you can perform multiple updates atomically,...
# spicedb
n
> well, you can perform multiple updates atomically, so that shouldn't be the primary concern, but I do see why you want it to be simpler What happens in one update if a subset of the relations don't exist and I try to delete them? Also I'm looking closer at your schema. It does simplify things, but it requires a bidirectional relationship. For example, I need to both set
document::visibility
and
visibility::parent
relationships. Is there a way to avoid such a cyclic dependency?