This is a bug and it was introduced with v0.9.0 because json_each has a parent field and it conflicts with the rel column. We'll need to prefix it. I'll try to add a test and will make a new release shorty after that.

@synapse A fix was released in v0.9.2. Please let me know if you are still experiencing issues after the update.

hey @ganigeorgiev all good now, works as expected 👍 .
Thanks a lot for the quick fix!

Hi i'm currently experiencing this issue with v12.2

Is there a fix for it?

@Jeffreyon
What exactly is the returned error?
Could you elaborate a little more on your collections structure?
If the error is the same as the above, could you confirm that your records don't have a required relation reference anywhere?

A "required relation reference" means that a relation field cannot be empty.

If replies or questions have a "Nonempty" (aka. required) relation field then you can't delete a user because on user delete we clear the related field values to their zero-defaults (empty string or array). The "Cascade" option is only for deleting the entire record, aka. on user delete -> delete also the related record, which I assume should be the expected behavior in your case and you should set it to true (this is why it also works when you delete first the replies and then the question, but if you set the Cascade to true, then this will happen automatically).

If that's not the case, please export your collections structure as json and attach it here (Admin UI > Settings > Export collections).

I can relate to this problem myself where I know there are relations between tables but it would be nice to have like a more verbose error message saying something like: record cannot be deleted because of this relation on field and this table. I am using multi relational table where I might have more then 5 relations and it's gets tricky to catch which one is blocking the deletion. In fact I've adopted a method to just add a new column called deleted and an API filter that goes with it to mark something as deleted. This helped me when I was trying to delete a record with circular references and deletion order.

@synapse There is already a more detailed error message in the Admin UI > Logs and/or when you start PocketBase with --debug. Eventually, we may propagate and print it also to the end user but someone could argue that this may lead to involuntary information disclosure about the internals of your data.

Yes that's true. I was only talking about a more detailed message for the admin panel and not for the API response.