You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jinxcifer Welcome back. The _removed field was either created by this project's previous contributor (who we have removed completely and severed all ties), or it's part of ArangoDB. I'm not totally sure, to be honest. The createdAt and updatedAt are also new keys this ORM adds, if you're wondering.
It sounds like we could use a user.hardDelete or user.forceDelete() or user.dangerouslyForceDelete().
If you want to get involved (you don't have to code), you can experiment with how Arango deals with missing records, or whether other ORMs use the _remove field. Telling me this information would save me a lot of time and help implement the change quickly.
Hi again!
I currently have the situation where I have a user ID and I want to delete that user from the database. I have the following two questions:
This will result in two database queries, right? Is there another way to do it in just one query, f.e.
User.remove(_id);
?Model.remove(model)
or
Model.prototype.remove()
it only changes the removed flag from false to true. Is there a way to hard delete the user from the database as well?
Thanks in advance!
Best regards,
jinxcifer
The text was updated successfully, but these errors were encountered: