http://in.relation.to/2018/07/04/hibernate-orm-5115-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On Wed, Jul 4, 2018 at 11:46 AM Emmanuel Bernard
wrote:
> Having the create-warn by default and allowing the user to move to
> create or fail is a good compromise. Vlad, in the documentation, we can
> have a get ready for production section that mention this problem and
> many others :)
>
OK, do
Let's keep this consistent and use the create-warn for all cases.
I understand why the user raised the original JIRA, and yes on paper,
failing is the safer prod friendly option.
But we must cater to the ease of development too. The development
workflow and experience is an important aspect that we
Any thoughts on this one? Luis, I think your opinion would help.
replace() being currently final, we cannot override it in child classes so
I tried another approach trying to avoid breaking what has been exposed to
the users:
https://github.com/hibernate/hibernate-orm/pull/2390
It's not pretty bu
Hi,
Current status:
- short names and compatibility layer on the ORM side: merged
- Radim will get the Infinispan region factory up to speed (Thanks!)
- we merged the configuration knobs to allow the automatic creation of
caches:
. default for Ehcache: create-warn: cache will be automatically crea
