Looking for a reasonable way to delete posts

For example, my program wants to provide the function of deleting posts
The post contains (pictures, text, and comments on the post)
My original idea is to use a function to delete the picture text first and then comment
However, this The code of the function is very long, almost more than 100 lines, and it is also difficult to maintain later. The pile of if else makes me dizzy. And if there is an execution error somewhere in the middle, it will be troublesome. When I delete the picture, I call the Qiniu interface to delete it, so the possibility of network failure cannot be ruled out

So I hope the master can provide a design idea to facilitate later maintenance and perfectly solve accidents

Reply content:

For example, my program wants to provide the function of deleting posts
The post contains (pictures, text, and comments on the post)
My original idea is to use a function to delete the picture text first and then comment
However, this The code of the function is very long, almost more than 100 lines, and it is also difficult to maintain later. The pile of if else makes me dizzy. And if there is an execution error somewhere in the middle, it will be troublesome. When I delete the picture, I call the Qiniu interface to delete it, so the possibility of network failure cannot be ruled out

So I hope the master can provide a design idea to facilitate later maintenance and perfectly solve accidents

If the post contains pictures, text, comments and other related information.
Then if you want to delete them you must write the relevant sql statements of delete picture, delete text, delete comment. This is unavoidable.
Then the remaining question is how to expand and maintain such functions: I strongly recommend writing an observer mode, which will trigger the deletion of images when the post deletion operation is triggered. , related operations of text and comments. In this way, it is easy to expand and maintain. After all, one method corresponds to one method, and there is no need to write so many if judgments.

Tips: It is best not to use transactions. Posts are not sensitive information, so even if an error occurs during the deletion process, it will not have any impact (it is just that the database information will become confusing and incomplete). Speeding up is the best way. Important

You can set a status for the post Show Hide Delete

When deleting, it is only set to the deletion state and is not displayed in the frontend

Then put a scheduled execution script and then completely delete the posts whose status is deleted

Now all deletions are logical deletions, why do we need to do physical deletions?

In fact, the stability of 7Niu is very good. You don’t have to worry too much about network problems. Of course, you can also add a deleted field to the table where these files are located. When you start deleting, change it locally to 1, and then delete it remotely. After the callback function actually deletes, otherwise wait for the scheduled task to clean up the data with deleted=1 twice.
As for text, comments, etc., it is actually best to use foreign keys to associate them with your posts, so that they are deleted directly in cascade without any additional processing. Or the ORM class framework can specify dependencies when declaring the model and automatically complete cascade deletion. Manual processing is really unsatisfactory anyway.

This is a bit troublesome to implement on the front end, especially when using third-party interfaces. We have to manually call multiple deletion methods. It will be a sour experience if we encounter batch deletion again.
Later I simply didn’t delete it because it wasn’t a big file anyway.

Do not delete the data. . Don’t delete