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
Add soft delete support.
Soft deleting is when you simply mark an attribute like is_deleted=True and ignoring it in the next queries instead of actually deleting it.
Describe your usecase
No usecase, I think I'd be cool. Also, It's an old friend's idea.
Describe the problem
When deleting any entity, you actually delete it from the database. This data is not recoverable.
Solution proposed
I was thinking about boolean fields having a soft_delete=True keyword.
Also, maybe have a class property like soft_delete='field_name' but I don't quite like it.
How about having different soft delete strategies and have the user choose one?:
Good old is_deleted=True (normal soft delete)
Change the entity kind to a entity-deleted one. This way queries won't be slowed down because of a large amount of data. Win win, but could be a pain if not optional.
Add soft delete support.
Soft deleting is when you simply mark an attribute like
is_deleted=True
and ignoring it in the next queries instead of actually deleting it.Describe your usecase
No usecase, I think I'd be cool. Also, It's an old friend's idea.
Describe the problem
When deleting any entity, you actually delete it from the database. This data is not recoverable.
Solution proposed
I was thinking about boolean fields having a
soft_delete=True
keyword.Also, maybe have a class property like
soft_delete='field_name'
but I don't quite like it.How about having different soft delete strategies and have the user choose one?:
is_deleted=True
(normal soft delete)entity-deleted
one. This way queries won't be slowed down because of a large amount of data. Win win, but could be a pain if not optional.Examples, links...
The text was updated successfully, but these errors were encountered: