Mark Paluch

So far we have the following usages that seem affected: * Hibernate `BaseUserTypeSupport` * `@Convert`

The JPA metamodel doesn't contain details about classes that are converted. This is opening up an entirely different problem space. As workaround, you can introduce another constructor (that is visible...

> Is there going to be a fix for this in 3.5.7 No, I don't think so, see https://github.com/spring-projects/spring-data-jpa/issues/3929#issuecomment-3044026015 As of now, we don't have the bandwidth nor reasonable contributions...

At the moment, Spring Data JDBC isn't ready for prime time with multiple data sources. The repository setup starts breaking apart once using relations (e.g. `List`) because the factory bean...

The underlying issue is to some extend how much mapping shall be considered for projections. Customized field naming in an entity should be ideally applied to avoid repetitive aliasing in...

Care to attach the full stack trace?

Looks like another incarnation of #4994. @jonatan-ivanov these reports seem to pile up. It's inconvenient to handle `MeterRegistry`-specific requirements in the observation code, especially because we're not familiar with these...

StatelessSession is currently a Hibernate-only concept. Chances stand well that the stateless-session concept will be included in the JPA 4.0 spec giving us an opportunity to explore a stateless repository...

Zooming out, what benefits do you get from using a stateless session? Hibernate's stateless session is stateful during query execution and once the query returns objects, then objects get detached.

Care to provide a reproducer? This seems a rather specific bug. While not necessarily the cause, the rendered SQL mentions the `submissions` table while you've included the `AppUser` entity.