Well, as I said at the other pr, I prefer logic deletion over physical deletion. Its easier to implement and you can always rollback

But this implementation is using soft deletion: https://github.com/csokol/mamute/blob/deleting-users/src/main/java/org/mamute/model/User.java#L50

Even this query?

session.createSQLQuery("delete from Answer_Comments where comments_id=:id")
         .setParameter("id", comment.getId()).executeUpdate();

Well, in this case I had to delete the data from the relationship table because hibernate was not so smart to ignore logically deleted comments when querying answers/questions joined with its comments. I can try to add where comment.deleted = false everywhere, but I think we would need to always remember to do that on complex queries. What do you think?

Well, I don't know if it will be hard or not to ignore all of them, but if we used left joins they should be ignored automatically if their relationships are, right?
I mean, the idea of using logical deletion is that we can undo the deletion if we want, but if you delete the relation table lines it would be much harder

They can't be ignored on left joins since the row still exists after deletion and hibernate is not smart enough to add where deleted=false automatically for joins. I'll try to track all the queries we are joining the comments and add this condition but I still think this will be ugly since we we'll need to remember to add this predicate forever.

Hi Leo, I removed that query from CommentDAO and added the logic to ignore deleted questions. I'm merging this one!