From bce4e7b0bb7f75eef41ef89099a32e258baf191b Mon Sep 17 00:00:00 2001 From: Christoph Strobl Date: Wed, 25 Oct 2023 11:02:41 +0200 Subject: [PATCH] capture thoughts on domain type collation resolution --- .../repository/support/DefaultRepositoryActionPreparer.java | 2 ++ 1 file changed, 2 insertions(+) diff --git a/spring-data-mongodb/src/main/java/org/springframework/data/mongodb/repository/support/DefaultRepositoryActionPreparer.java b/spring-data-mongodb/src/main/java/org/springframework/data/mongodb/repository/support/DefaultRepositoryActionPreparer.java index d66aad979..7c09843e7 100644 --- a/spring-data-mongodb/src/main/java/org/springframework/data/mongodb/repository/support/DefaultRepositoryActionPreparer.java +++ b/spring-data-mongodb/src/main/java/org/springframework/data/mongodb/repository/support/DefaultRepositoryActionPreparer.java @@ -65,6 +65,8 @@ public class DefaultRepositoryActionPreparer implements RepositoryActionPreparer metadata.getReadPreference().ifPresent(it -> action.getQuery().withReadPreference(it)); if (!action.getQuery().getCollation().isPresent()) { metadata.getCollation().map(this::resolveCollation) + // should we even bother about the domain type collation here? + // the template API will add it if not present anyway. .or(() -> Optional.ofNullable(action.getDomainTypeInformation().getCollation())) .ifPresent(it -> action.getQuery().collation(it)); }