hibernate-5.x

问题 I have following code that I need to refactor for use in hibernate 5. This includes removing every deprecated call. public List<T> findByExample(T example, String... excludeProperty) { Criteria crit = session.createCriteria(T.class); Example ex = Example.create(example); for (String exclude : excludeProperty) { ex.excludeProperty(exclude); } crit.add(ex); return crit.list(); } Since createCriteria is deprecated I was going to replace it with getSession().getCriteriaBuilder().createQuery(Foo

问题 Hibernate 5 and above supports Java8 DateTime Api through jar "hibernate-java8". But the MavenRepository shows a message Deprecated - use hibernate-core instead) alongside the title of the hibernate-java8 jar. Why is the hibernate-java8 jar called deprecated even though it is required to gain the hibernate support for java8? 回答1: You can see the Migration Guide for Hibernate. It specifies that Hibernate 5.2 is built using Java 8 JDK and will require Java 8 JRE at runtime (we are investigating

问题 after upgrading hibernate to from version 4.3.7.Final to 5.3.18.Final I got the error below @Entity @Audited @AuditPermission(Permission.VIEW_INDIVIDUAL) public class Individual implements ITemporalEntity { @Id @Column(name = "Individual_id") @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "Individual_generator") @SequenceGenerator(name = "Individual_generator", initialValue = 1, allocationSize = 1, sequenceName = "Individual_id_seq") private Long id; @Embedded private

来源： https://stackoverflow.com/questions/44480415/where-is-the-reverse-engineering-feature-in-hibernate5

问题 When I do anything with a table, it always show the error: Hibernate: select nextval ('hibernate_sequence') 2019-07-20 16:15:44.877 WARN 58376 --- [nio-9000-exec-1] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 0, SQLState: 42P01 2019-07-20 16:15:44.877 ERROR 58376 --- [nio-9000-exec-1] o.h.engine.jdbc.spi.SqlExceptionHelper : ERROR: relation "hibernate_sequence" does not exist I DON'T want to use hibernate_sequence to share id sequence between tables, but want to define id seq for each

问题 I need a help to migrate the code with createCriteria for Hibernate 5 , the code is this below: public Curso comDadosIguais(Curso curso) { return (Curso) this.session.createCriteria(Curso.class) .add(Restrictions.eq("codigo", curso.getCodigo())) .uniqueResult(); } Could you help me? 回答1: There are a number of options you can exercise to migrate from the deprecated Hibernate Criteria API, these are just a few that immediately come to mind: HQL / JPQL Named query JPA Criteria API From a HQL /

问题 I need a help to migrate the code with createCriteria for Hibernate 5 , the code is this below: public Curso comDadosIguais(Curso curso) { return (Curso) this.session.createCriteria(Curso.class) .add(Restrictions.eq("codigo", curso.getCodigo())) .uniqueResult(); } Could you help me? 回答1: There are a number of options you can exercise to migrate from the deprecated Hibernate Criteria API, these are just a few that immediately come to mind: HQL / JPQL Named query JPA Criteria API From a HQL /

问题 When saving a LocalDate field (e.g. '2017-09-27') to a mySQL Date column using JPA CriteriaBuilder API, the result is different (e.g. '2017-09-26'). I have validated that my database's timezone is set to UTC using SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP) as the result is '00:00:00'. I am testing this locally, and I have a timezone of GMT + 2, so my suspicion is that when the conversion occurs from LocalDate to Date , 2 hours are being deducted and producing a date 1 day before the requested date

问题 When saving a LocalDate field (e.g. '2017-09-27') to a mySQL Date column using JPA CriteriaBuilder API, the result is different (e.g. '2017-09-26'). I have validated that my database's timezone is set to UTC using SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP) as the result is '00:00:00'. I am testing this locally, and I have a timezone of GMT + 2, so my suspicion is that when the conversion occurs from LocalDate to Date , 2 hours are being deducted and producing a date 1 day before the requested date

问题 When saving a LocalDate field (e.g. '2017-09-27') to a mySQL Date column using JPA CriteriaBuilder API, the result is different (e.g. '2017-09-26'). I have validated that my database's timezone is set to UTC using SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP) as the result is '00:00:00'. I am testing this locally, and I have a timezone of GMT + 2, so my suspicion is that when the conversion occurs from LocalDate to Date , 2 hours are being deducted and producing a date 1 day before the requested date