infobip-spring-data-querydsl
infobip-spring-data-querydsl copied to clipboard
infobip
Infobip Spring Data Querydsl provides new functionality that enables the user to leverage the full power of Querydsl API on top of Spring Data repository infrastructure.
```java @NoRepositoryBean public interface ExtendedCommonEntityDataPolicyDao< T extends AbstractPersistableEntity, Q extends EntityPath > extends ExtendedQuerydslJpaRepository, QuerydslBinderCustomizer { // ... } ``` ```java @Repository @Primary public interface SysGrpDao extends ExtendedCommonEntityDataPolicyDao { /*...
```SimpleQuerydslR2dbcFragment ``` and ```ReactiveQuerydslR2dbcPredicateExecutor``` do not use prepared statement bindings but literals. is there any reason for ```setUseLiterals(true)```? https://github.com/infobip/infobip-spring-data-querydsl/blob/c1b6926919520b70c8fa2f40e59ad2afca3de489/infobip-spring-data-r2dbc-querydsl/src/main/java/com/infobip/spring/data/r2dbc/SimpleQuerydslR2dbcFragment.java#L67 https://github.com/infobip/infobip-spring-data-querydsl/blob/ead317f5fb782178913a90798c420be00c5f8e12/infobip-spring-data-r2dbc-querydsl/src/main/java/com/infobip/spring/data/r2dbc/ReactiveQuerydslR2dbcPredicateExecutor.java#L138
when i query then error " java.lang.UnsupportedOperationException: named binding is not supported by jasync driver ?=In{Inferred: java.lang.Long} at com.github.jasync.r2dbc.mysql.JasyncStatement.bind(JasyncStatement.kt:65) Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException. " use: spring boot 3.1.3 jasync-r2dbc-mysql 2.2.4 infobip-spring-data-r2dbc-querydsl-boot-starter 9.0.2...
I forked the project and found that the configuration of the Embedded annotation is upstream, and since the upstream does not handle data-jdbc, this needs to be handled by infobip-querydsl-apt....
Thanks for your amazing project, I feels exceptionally smooth when using r2dbc and querydsl, so I strongly recommend it to my colleagues. However, I have a small question I'd like...
The build task will fail when an entity is defined as a nested class. For example, say we have some classes like: ``` class A { // any code @Table("table_b")...
It seems that QueryDSL's development is again slowing down significantly. Important dependency updates are being ignored. Driver dependencies (e. g. for PostgreSQL) are quite old. The spatial support for Postgis...
