Issues

IN clause with more than 1000 expressions

Failing to update a one-to-one lazy association with `OptimisticLockType.DIRTY` and enabled bytecode enhancement

Bytecode enhancement leads to broken constructor for a generic embedded field in a MappedSuperclass

Revisit logging statement that use string concat for formatted logging

JPQL IN clause gives error if you use interface for entity Could not locate TableGroup

Fail to delete entity that contains an embedded with a many to many association as field

When batching enabled the LockModeType is ignored

Using bytecode enhancement may result in incorrect AccessType being picked

With Bytecode enhancement a lazy ManyToOne association targeting an Entity annotated with @Proxy(lazy = false) is eagerly loaded

@MappedSuperclass with parameterized interface types no longer works

StackOverflowError when loading a ManyToOne whith @Proxy(lazy=false)

Doing polymorphic queries with interfaces results in exception SqmRoot not yet resolved to TableGroup

HQL with subquery with entity path at least two levels deep produces wrong SQL

Unexpected warning: "HHH100001: JDBC driver did not return the expected number of row counts"

Reading entities using @MappedSuperclass does not work with classes in foreign packages

"persister" is null during validation with lazy collections

Treated join in subquery results in invalid SQL

NPE When initializing a lazy collection during flush

In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000

Alias XXX used for multiple from-clause elements error when executing query with 2 level join

Wrong SQL generated when root join is not used in sub-query

Property sorting can lead to incorrect column mappings with derived embeddable keys

LockTest.testLock*FkTarget fail on Sybase with timeout getting lock

@ElementCollection + nested @Embeddable -> @Enumerated ignored

Hibernate returns duplicates into @OneToMany collection after merge