QueryDslJdbcTemplate#queryForObject(SQLQuery, ExpressionBase<T>) should accept Expression<T> as 2nd param [DATAJDBC-34] #291
Comments
mp911de
added a commit
that referenced
this issue
Feb 21, 2022
We now use SqlIdentifier to encapsulate the table and column name across the API. The fluent DatabaseClient API accepts the table name and select column projections as SqlIdentifier. The Criteria API remains String-based as names for Query and Update objects may reference either column names or property names. QueryMapper and UpdateMapper require now a R2DBC dialect object to be constructed. R2dbcMappingContext is configured in a way to not require quoting to preserve backwards compatibility.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ryo murai opened DATAJDBC-34 and commented
QueryDslJdbcOperations#queryForObject(SQLQuery, ExpressionBase<T>)
breaks a spec described its javadoc: The results are mapped using the {
@linkExpressionBase} which could be a QBean or a MappingProjection.Because QBean(extends RelationalPathBase) is not an ExpressionBase but Expression, I can't pass a QBean object as ExpressionBase. The compilation fails at below line.
template.queryForObject(sqlQuery, QBeanObj)
Affects: Ext 1.0 M2
Reference URL: https://github.com/SpringSource/spring-data-jdbc-ext/blob/master/spring-data-jdbc-core/src/main/java/org/springframework/data/jdbc/query/QueryDslJdbcTemplate.java#L206
Referenced from: commits spring-attic/spring-data-jdbc-ext@3225617
1 votes, 2 watchers
The text was updated successfully, but these errors were encountered: