multipart.maxFileSize=10000000
multipart.maxRequestSize=10000000

spring.jpa.hibernate.ddl-auto=update
flyway.baseline-on-migrate=true

logging.level.org.hibernate=WARN
logging.level.org.marsik.elshelves.backend.services=INFO

spring.datasource.url=jdbc:mysql://localhost/elshelves_test?useUnicode=yes&characterEncoding=UTF-8
spring.datasource.username=root
spring.datasource.password=
spring.datasource.driver-class-name=com.mysql.jdbc.Driver

spring.jpa.hibernate.naming_strategy: org.hibernate.cfg.ImprovedNamingStrategy
spring.jpa.database-platform=org.hibernate.dialect.MySQL5InnoDBDialect

hystrix.streamEnabled = true

multipart.maxFileSize=10000000
multipart.maxRequestSize=10000000

spring.jpa.hibernate.ddl-auto=update
flyway.baseline-on-migrate=true

logging.level.org.hibernate=WARN
logging.level.org.marsik.elshelves.backend.services=INFO

spring.datasource.url=jdbc:mysql://localhost/elshelves_test?useUnicode=yes&characterEncoding=UTF-8
spring.datasource.username=root
spring.datasource.password=
spring.datasource.driver-class-name=com.mysql.jdbc.Driver

# The COMMIT flush mode is necessary for relinking
spring.jpa.properties.org.hibernate.flushMode=COMMIT
spring.jpa.hibernate.naming_strategy: org.hibernate.cfg.ImprovedNamingStrategy
spring.jpa.database-platform=org.hibernate.dialect.MySQL5InnoDBDialect

hystrix.streamEnabled = true

Change the default flush mode to COMMIT
Change the default flush mode to COMMIT

Relinked object is in inconsistent state during the operation so any
flush will cause constraint violation.

The relinker is mixing queries and updates to the relinked object and
all queries generate flushes in the AUTO setting.

This change modifies hibernate default to use COMMIT that causes flush
operation only when the transaction is about to be commited.

Manual flush can be used in cases when a transient object is supposed
to be included in query results (relinker does not need this as it
maintains its own internal cache which is consulted first).
