@steep-lamp-91158 Hey Patrik. I know you were active on the feature request for uuid mappings, so I wanted to ask here.....Probably due to ignorance I have some keto relations for list endpoints

<http://mydomain.com/tickets|mydomain.com/tickets>

for example with an empty

Object

. With

v0.9.0-alpha.0

I receive a violation constraint due to an empty object I believe (requests with an object work fine). Is there a correct way to handle these types of endpoints when no object actually exists when querying for all tickets as an example? Error

"message": "ERROR: new row for relation \"keto_uuid_mappings\" violates check constraint \"keto_uuid_mappings_string_representation_check\" (SQLSTATE 23514)",

Current Relation

{
	Action: rts.RelationTupleDelta_ACTION_INSERT,
	RelationTuple: &rts.RelationTuple{
		Namespace: namespace,
		Object:    "",
		Relation:  "LIST",
		Subject:   rts.NewSubjectID(subject),
	},
},

Is the empty object something like all objects semantically? I'd recommend to instead use e.g.

"*"

as the object in that case

Yes it is. Okay I think that will work. Thank you very much.