Jens Schauder
Jens Schauder
Yes, that should work.
Query derivation is currently only supported for direct properties. There should be already a ticket for this I think, but I can't find it. Sorry for the somewhat misleading documentation....
We currently do not have a timeline for this.
> `CryptoExchanges(null, null)` Should generates this request : `INSERT INTO "common"."CryptoExchanges" VALUES (DEFAULT, DEFAULT);` Why should it create two `DEFAULT` entries? `DEFAULT` should only be used for id columns, shouldn't...
It looks like Spring Data JDBC isn't able to obtain the parameter name for the constructor parameter from the byte code. For Java there is a compiler flag to ensure...
I agree we should support the use of exception translators. Therefore the `JdbcAggregateTemplate` should invoke the exception translation handling.
`QueryMappingConfiguration` is intended for custom queries only. Interesting idea to apply it to the methods of the predefined methods as well. Could you explain why you need a custom `RowMapper`...
Can't you do the same with a custom conversion for the column/type?
This is handled by `@ReadingConverter` and `@WritingConverter`. Let's say you have a `@WritingConverter` from `Person` to `String` and a `@ReadingConverter` in for the inverse conversion. The writing converter would be...
When we created the option to use row mappers with `@Query` it was intended for specialised queries that were not intended for CRUD operation. Using row mappers for the standard...