Batch inserts via EntityManager

Author: AnghelLeonard

HibernateSpringBootBatchInsertsEntityManager/README.md

@@ -4,17 +4,18 @@
 **Description:** Batch inserts via `EntityManager` in MySQL. This way you can easily control the `flush()` and `clear()` of the persistence context (1st level cache). This is not possible via SpringBoot, `saveAll(Iterable<S> entities)`. Another advantage is that you can call `persist()` instead of `merge()` - this is used behind the scene by the SpringBoot `saveAll(Iterable<S> entities)` and `save(S entity)`.
 
 **Key points:**\
-     - in application.properties set `spring.jpa.properties.hibernate.jdbc.batch_size`\
-     - in application.properties set `spring.jpa.properties.hibernate.generate_statistics` (just to check that batching is working)\
-     - in application.properties set JDBC URL with `rewriteBatchedStatements=true` (optimization for MySQL)\
-     - in application.properties set JDBC URL with `cachePrepStmts=true` (enable caching and is useful if you decide to set `prepStmtCacheSize`, `prepStmtCacheSqlLimit`, etc as well; without this setting the cache is disabled)\
-     - in application.properties set JDBC URL with `useServerPrepStmts=true` (this way you switch to server-side prepared statements (may lead to signnificant performance boost))\
+     - in `application.properties` set `spring.jpa.properties.hibernate.jdbc.batch_size`\
+     - in `application.properties` set `spring.jpa.properties.hibernate.generate_statistics` (just to check that batching is working)\
+     - in `application.properties` set JDBC URL with `rewriteBatchedStatements=true` (optimization for MySQL)\
+     - in `application.properties` set JDBC URL with `cachePrepStmts=true` (enable caching and is useful if you decide to set `prepStmtCacheSize`, `prepStmtCacheSqlLimit`, etc as well; without this setting the cache is disabled)\
+     - in `application.properties` set JDBC URL with `useServerPrepStmts=true` (this way you switch to server-side prepared statements (may lead to signnificant performance boost))\
      - in case of using a parent-child relationship with cascade persist (e.g. one-to-many, many-to-many) then consider to set up `spring.jpa.properties.hibernate.order_inserts=true` to optimize the batching by ordering inserts\
      - in entity, use the [assigned generator](https://vladmihalcea.com/how-to-combine-the-hibernate-assigned-generator-with-a-sequence-or-an-identity-column/) since MySQL `IDENTITY` will cause batching to be disabled\
-     - in DAO, flush and clear the persistence context from time to time. This way you avoid to "overwhelm" the persistence context. 
+     - in DAO, flush and clear the persistence context from time to time; this way you avoid to "overwhelm" the persistence context\
+     - if is not needed then ensure that Second Level Cache is disabled via `spring.jpa.properties.hibernate.cache.use_second_level_cache=false`
 
 **Output example:**
-![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchInsertsEntityManager/sample.png)
+![](https://github.com/AnghelLeonard/Hibernate-SpringBoot/blob/master/HibernateSpringBootBatchInsertsEntityManager/batch%20inserts%20via%20EntityManager.png)
 
 --------------------------