4.7 (116) In stock
Describe the bug Tried using the latest Quarkus 2.1.0.RC and hibernate reactive panache. On @OneToMany and @ManyToMany. Looks like an issue with FetchType.LAZY as if I manually specify FetchType.EAGER it works. Tried wrapping it in Panac
Broken context propagation in HTTP request that involves hibernate-reactive- panache, resteasy-reactive and qute · Issue #27229 · quarkusio/quarkus · GitHub
Quarkus REST Reactive ServerRequestFilter Has To Be Blocking When Using With Hibernate Panache Reactive · Issue #21215 · quarkusio/quarkus · GitHub
quarkus-hibernate-validator HV000149: http 500 error caused by IllegalArgumentException if accept-language is invalid · Issue #33150 · quarkusio/quarkus · GitHub
GitHub - dvddhln/quarkus-reactive-hibernate-graphql-crud: Reactive Hibernate ORM and Panache with smallrye-graphql
quarkus-hibernate-reactive-panache does not work with scheduler · Issue #31132 · quarkusio/quarkus · GitHub
Hibernate collections initialized on call to getMyCollection · Issue #17291 · quarkusio/quarkus · GitHub
Hibernate Reactive with Panache : transaction rollback should trigger session re-creation · Issue #24499 · quarkusio/quarkus · GitHub
Panache Rx · Issue #2198 · quarkusio/quarkus · GitHub
Hibernate Reactive with Panache error · Issue #23283 · quarkusio/quarkus · GitHub
Improve error message when lazy collection is not initialized · Issue #1205 · hibernate/hibernate-reactive · GitHub