AleksNo

Hi, the constructors of the wrapper types are now deprecated for removal. Code which uses those constructors will not compile anymore when they remove them. https://docs.oracle.com/en/java/javase/16/docs/api/java.base/java/lang/Boolean.html Cheers

Hello, i like the idea. :) Cheers

Hi, the problem with this change is, it could break the backwards compatibility in some cases. Working with detached entities is such a case if the code relies on it,...

Hi. True, @NamedEntityGraph is almost unusable. It is ugly and it becomes very messy very quickly. Especially if you want more than one @NamedEntityGraph on an Entity. I use dynamic...

Hello, removing the no-arg constructor requirement would have one big advantage: better interoperability with other programming languages. In Kotlin it is not possible to make a class with a no-arg...

Hello, personally i prefer stronger type safety if it does not make the API or implementations way more complicated. This is one of the most important features of the criteria...

Maybe it is a good idea to collect very common options like fetchsize, batchsize, batchtype (IN, JOIN, Subquery, EXISTS etc.), cache size etc. and make them a part of the...

Java records are not valid entities. So the results are implementation specific and may vary. Try classes instead of records.

OK, i have read the description of this Exception: https://docs.oracle.com/javaee%2F6%2Fapi%2F%2F/javax/persistence/EntityExistsException.html "Thrown by the persistence provider when EntityManager.persist(Object) is called and the **entity** already exists." I guess, it is meant, that...

Hello, the reason might be because you use long as an id. So if there is already a child with the id 0 in the database then you cannot insert...