feat: Support adding @YdbType annotation to method parameters

[zdazzy]

To cover the following (and all similar) case:

interface MyRepository extends ListCrudRepository<MyEntity, String> {

    @Query(
        """
        SELECT <....>
        <....>
        LIMIT :limit
        """
    )
    List<MyEntity> findWithLimit(@Param("limit") long limit);

}

The inferred limit parameter type here is Int64, while YDB requires it to be exaclty UInt64.

There are other cases where implicit type conversion fails. So a way to control this behavior would be great. An existing @YdbType annotation seems like a good solution.

[mipo256]

@zdazzy Existing YdbMappingJdbcConverter should solve this. This custom JdbcConverter is applied on both named and positional parameters.

Have you extended the AbstractYdbJdbcConfiguration?

[zdazzy]

@mipo256 The annotation is currently only applicable to fields. Placing it on method parameter will result in a compilation error.
The issue has nothing to do with configuration.

[mipo256]

Yes, I got the general idea of what you're trying to do.

CC: @KirillKurdyukov please, add the pending-design tag for the issue

[mipo256]

The first top-level review of the problem unravels the following approach.

We can specify the custom RepositoryFactoryBeanSupport in the @EnableJdbcRepositories, extended from JdbcRepositoryFactoryBean likely. We need it to override the creation of the JdbcRepositoryFactory child that has it's own QueryLookupStrategy defined. And here, we can construct our own QueryMethod with our own implementation of getParameters().

That would solve the problem. However, there are a couple of caveats.

1. This would require to extend a lot of stuff from the original Spring Data Commons/Spring Data JDBC infrastructure. That is generally not a big deal, since it is designed in this way specifically
2. The larger problem is that the JdbcQueryLookupStrategy that is native to Spring Data JDBC, like CreateIfNotFoundQueryLookupStrategy, which is used by default, is not a public API. Therefore, we would have to extend RelationalQueryLookupStrategy and duplicate some code from the original source tree.

So, we need to think about it more deeply.

CC: @KirillKurdyukov

[mipo256]

Related spring-projects/spring-data-relational#1998