cascading deletions are actually performed
but in practice, it is this kind of pseudo deletion that creates flag and assigns 0,1
.is there a callback method that can handle the logic of deletion? Only in this way can we write custom delete logic
how do you deal with similar problems
-split line-
assume that my entity class is Parent, and use @ SQLDelete to modify it
@ SQLDeleteAll, @ SQLInsert, @ SQLUpdate