FWIW, using postgres triggers to transform app data into rows in

relation_tuple

is working pretty well, from preliminary tests. However, I'm wondering if we couldn't set that up as a view instead. IOW, I'd run the migrations, then delete

relation_tuple

and recreate it as a view on app tables. What I'm concerned we'd run into, however, is a lack of consistent values for the

created_transaction

and

deleted_transaction

columns, and possible issues with SpiceDB expecting a writable table.