Delete with returning

[AmineZouitine]

PR Info

• Closes [ADD]: Addition of delete many #615

• Dependencies:
  • N/A

• Dependents:
  • N/A

New Features

• Addition of method to DeleteOne structure that returns the deleted element. I based this implementation on the update method.

Bug Fixes

• N/A

Breaking Changes

• N/A

Additional information

The Pull Request doesn't fully match the issue. After reviewing the entire code, I've taken the initiative to stay within the scope of the existing code, particularly the executor/update, which also defines a way to retrieve an element with the "RETURNING" feature.

Tests

Here

I have written two tests to verify the proper functioning of the new feature:

• delete_one_with_returning: This test verifies that the model is correctly retrieved after a delete operation.
• delete_one_with_returning_not_exist: This test ensures that the program triggers the correct error when the entry does not exist.



[billy1624]

Hey @AmineZouitine, thanks for contributing!!

I think it's better to enable Deleter to execute a delete statement while returning a single model or vector of model.

I imagine there could be two new methods in the Deleter:

1. async fn one(mut self, db: &C) -> Result<Model, DbErr>
2. async fn all(mut self, db: &C) -> Result<Vec<Model>, DbErr>

Both methods did the same thing except that it yields single / multiple Model. For DB that support returning it should add returning expression to the DeleteStatement.

Otherwise, if the DB does not support returning. We need to extract the WHERE condition from the delete statement, construct a select statement based on that and then query the rows. Finally, return the selected rows after the delete statement has been executed.

[tyt2y3]

closed in favor of #2432