5 (690) · $ 11.50 · 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
Quarkus Superheroes Quarkus 2 -> 3 upgrade issues · Issue #31400 · quarkusio /quarkus · GitHub
Quarkus reactive core with Panache reactive and Panache JPA · Issue #21199 · quarkusio/quarkus · GitHub
Simplify JPA implementation with Hibernate Reactive with Panache in Quarkus
Scheduled task using Reactive Hibernate Resources · quarkusio quarkus · Discussion #27543 · GitHub
Hibernate reactive with panache exception when lazily loading a byte array · Issue #36211 · quarkusio/quarkus · GitHub
Under load Panache Reactive exception Detected use of the reactive session from a different Thread · Issue #34848 · quarkusio/quarkus · GitHub
Reactive Hibernate w/ Panache insert two entities within the same persistence context · Issue #23845 · quarkusio/quarkus · GitHub
Reactive hibernate Panache when set quarkus.datasource.reactive.max-size=1 quarkus unable to start · Issue #33776 · quarkusio/quarkus · GitHub
quarkus-hibernate-reactive-panache does not work with scheduler · Issue #31132 · quarkusio/quarkus · GitHub
Cannot add entity to lazy loaded collection with Quarkus Reactive Panache - org.hibernate.LazyInitializationException · Issue #23757 · quarkusio/quarkus · GitHub
Improve error message when lazy collection is not initialized · Issue #1205 · hibernate/hibernate-reactive · GitHub