Spring Data JPA VS Presto

Please note: The H2 database was chosen for simplicity. You can replace it with any other database technology and use the Spring Boot JPA to connect. The demo application will still work.

What you are trying to do is not supported in JPA/JPQL or Spring Data (see here) Not even all databases support that syntax as far as I'm aware. You either need to concat the columns or add functionality to do this yourself, perhaps a Hibernate UserType will work.

There was also a discussion in the Spring Data JPA project repo surrounding the documentation as well: https://github.com/spring-projects/spring-data-jpa/issues/2055

There is a small typo on the second issue, I have tried opening a PR myself to fix it https://github.com/spring-projects/spring-data-jpa/pull/2869. I hope i haven't messed up something lol.

data-jpa: Spring Data JPA, makes it easy to create JPA-based repositories

This repository is an example application for the Spring Boot framework that employs the Netflix DGS framework to expose a GraphQL API and that interacts with a PostgreSQL DBMS via Spring Data JPA.

I'm using Spring Data JPA as a persistence framework. Therefore, those classes are Hibernate entities.

By two different former developers, one from QueryDSL and the other RSQL JPA Spec (Criteria API), both mention that it is a Java issue mentioned here (since 2015...): https://github.com/spring-projects/spring-data-jpa/issues/1115

If you go with hibernate note that there are a few different ways to use it. It can be used standalone and it can be used as a JPA implementation. If you use Spring and use hibernate as a JPA implementation then a popular Spring data layer abstraction is Spring Data which has JPA support with its Spring Data JPA library (https://spring.io/projects/spring-data-jpa)

We have some of this functionality in Presto (https://github.com/prestodb/presto), but it takes fair bit of work to implement it for all the different backends.

Note that glibc has a similar problem in multithreaded contexts. It strands unused memory in thread-local pools, which grows your memory usage over time like a memory leak. We got lower memory usage that didn't grow over time by switching to jemalloc.

Example of this: https://github.com/prestodb/presto/issues/8993

I look at the grammar. Here is preto's grammar which is mostly similar to other sql engines: https://github.com/prestodb/presto/blob/master/presto-parser/src/main/antlr4/com/facebook/presto/sql/parser/SqlBase.g4

export MVNW_VERBOSE=true git clone https://github.com/prestodb/presto.git cd presto bash ./mvnw clean install

more specifically, recently started learning about Presto [paper], and have been diving deeper into [source] code.

Presto