Merge branch 'master' of https://github.com/AnghelLeonard/Hibernate-SpringBoot

Author: AnghelLeonard

HibernateSpringBootBatchDeleteCascadeDelete/README.md

@@ -1,20 +1,20 @@
-**[How To Batch Deletes In MySQL Via SQL "on delete cascade"](https://github.com/AnghelLeonard/Hibernate-SpringBoot/tree/master/HibernateSpringBootBatchDeleteCascadeDelete)**
+**[How To Batch Deletes In MySQL Via SQL "ON DELETE CASCADE"](https://github.com/AnghelLeonard/Hibernate-SpringBoot/tree/master/HibernateSpringBootBatchDeleteCascadeDelete)**
 
-**Description:** Batch deletes in MySQL via `on delete cascade`. Auto-generated database schema will contain `ON DELETE CASCADE` directive.
+**Description:** Batch deletes in MySQL via `ON DELETE CASCADE`. Auto-generated database schema will contain `ON DELETE CASCADE` directive.
 
-**Note:** Spring `deleteAllInBatch()` and `deleteInBatch()` don't use batching. The first one simply triggers a `delete from entity_name` statement, while the second one triggers a `delete from entity_name where id=? or id=? or id=? ...` statement. Rely on `delete()` method.
+**Note:** Spring `deleteAllInBatch()` and `deleteInBatch()` don't use *classical* delete batching. The first one simply triggers a `delete from entity_name` statement, while the second one triggers a `delete from entity_name where id=? or id=? or id=? ...` statement. Both of them take advantage on `ON DELETE CASCADE`. For *classical* delete batching rely on `deleteAll()`, `deleteAll(Iterable<? extends T> entities)` or `delete()` method. Behind the scene, the two flavors of `deleteAll()` relies on `delete()`.
 
 **Key points:**\
-     - in this example, we have a `Tournament` entity and each tournament can have several `TennisPlayer` (*one-to-many*)\
+     - in this application, we have a `Author` entity and each author can have several `Book` (*one-to-many*)\
      - first, we remove `orphanRemoval` or set it to `false`\
      - second, we use only `CascadeType.PERSIST` and `CascadeType.MERGE`\
      - third, we set `@OnDelete(action = OnDeleteAction.CASCADE)` next to `@OneToMany`\
      - fourth, we set `spring.jpa.properties.hibernate.dialect` to `org.hibernate.dialect.MySQL5InnoDBDialect`\
-     - fifth, we use the Spring `delete()` method to delete all `Tournament`
+     - fifth, we run through each `deleteFoo()` method
 
 **Output example:**
 
-![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchDeleteCascadeDelete/batch_delete.png)
+![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchDeleteCascadeDelete/batch%20delete%20via%20SQL%20cascade%20delete.png)
 
 -------------------------------
 

README.md

@@ -1086,23 +1086,23 @@ A `Previous Page` button can be implemented easily based on the first record.
 
 -----------------------------------------------------------------------------------------------------------------------    
 
-78. **[How To Batch Deletes In MySQL Via SQL "on delete cascade"](https://github.com/AnghelLeonard/Hibernate-SpringBoot/tree/master/HibernateSpringBootBatchDeleteCascadeDelete)**
+78. **[How To Batch Deletes In MySQL Via SQL "ON DELETE CASCADE"](https://github.com/AnghelLeonard/Hibernate-SpringBoot/tree/master/HibernateSpringBootBatchDeleteCascadeDelete)**
 
-**Description:** Batch deletes in MySQL via `on delete cascade`. Auto-generated database schema will contain `ON DELETE CASCADE` directive.
+**Description:** Batch deletes in MySQL via `ON DELETE CASCADE`. Auto-generated database schema will contain `ON DELETE CASCADE` directive.
 
-**Note:** Spring `deleteAllInBatch()` and `deleteInBatch()` don't use batching. The first one simply triggers a `delete from entity_name` statement, while the second one triggers a `delete from entity_name where id=? or id=? or id=? ...` statement. Rely on `delete()` method.
+**Note:** Spring `deleteAllInBatch()` and `deleteInBatch()` don't use *classical* delete batching. The first one simply triggers a `delete from entity_name` statement, while the second one triggers a `delete from entity_name where id=? or id=? or id=? ...` statement. Both of them take advantage on `ON DELETE CASCADE`. For *classical* delete batching rely on `deleteAll()`, `deleteAll(Iterable<? extends T> entities)` or `delete()` method. Behind the scene, the two flavors of `deleteAll()` relies on `delete()`.
 
 **Key points:**\
-     - in this example, we have a `Tournament` entity and each tournament can have several `TennisPlayer` (*one-to-many*)\
+     - in this application, we have a `Author` entity and each author can have several `Book` (*one-to-many*)\
      - first, we remove `orphanRemoval` or set it to `false`\
      - second, we use only `CascadeType.PERSIST` and `CascadeType.MERGE`\
      - third, we set `@OnDelete(action = OnDeleteAction.CASCADE)` next to `@OneToMany`\
      - fourth, we set `spring.jpa.properties.hibernate.dialect` to `org.hibernate.dialect.MySQL5InnoDBDialect`\
-     - fifth, we use the Spring `delete()` method to delete all `Tournament`
+     - fifth, we run through each `deleteFoo()` method
 
 **Output example:**
 
-![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchDeleteCascadeDelete/batch_delete.png)
+![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchDeleteCascadeDelete/batch%20delete%20via%20SQL%20cascade%20delete.png)
 
 -----------------------------------------------------------------------------------------------------------------------