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
Describe the bug or question
As far as I can tell, the soft delete columns are not taken into account when returning entries from the database using any of the get methods.
Description
When using the soft delete columns, they are set correctly when using the FastCRUD.delete() method. When retrieving objects however, it is not taken into account whether the object was soft deleted or not. Maybe this is an intentional design choice and wrong expectations on my side, but I was assuming that by default soft deleted objects would not be returned, potentially with an option to return them by using a parameter.
The text was updated successfully, but these errors were encountered:
It was an intentional design choice, I'm not sure if it's the most intuitive. If by default it excluded is_deleted=True, I think it would add complexity for the other cases (if you want to retrieve all of them and specially if you want to retrieve only deleted records).
For the second case we could end up with something like:
Describe the bug or question
As far as I can tell, the soft delete columns are not taken into account when returning entries from the database using any of the get methods.
Description
When using the soft delete columns, they are set correctly when using the
FastCRUD.delete()
method. When retrieving objects however, it is not taken into account whether the object was soft deleted or not. Maybe this is an intentional design choice and wrong expectations on my side, but I was assuming that by default soft deleted objects would not be returned, potentially with an option to return them by using a parameter.The text was updated successfully, but these errors were encountered: