#Unique Constraint Violation
1 messages · Page 1 of 1 (latest)
hi @stuck stream , this error typically occurs when you try to write the same relationship to the same tenant twice. Under what circumstances did you encounter this error message?
please take a look at this
#permify-help-archived message
I am writing the the schema in the NewPermify function
it seems like you are receiving this error because a same tenant is being created each time NewPermify is called.
But when starting without db (in memory) everything works fine.
Hi @stuck stream , 'in memory' doesn't persist data with each initialization - every time you start, the data gets erased. It is suitable for testing purposes.