TableRelationResolver<Q,R,TS,TQ,TR> |
TableRelationResolver.replaceTable(QueryTableMapping<? extends TS,TQ,TR> target) |
|
<AQ extends FlexibleRelationalPathBase<AR>,AS,AR>
TableRelationResolver<TQ,TR,AS,AQ,AR> |
TableRelationResolver.reverse(@NotNull QueryTableMapping<AS,AQ,AR> targetMapping) |
|
static <Q extends FlexibleRelationalPathBase<R>,R,TS,TQ extends FlexibleRelationalPathBase<TR>,TR>
TableRelationResolver<Q,R,TS,TQ,TR> |
TableRelationResolver.usingJoin(@NotNull Supplier<QueryTableMapping<TS,TQ,TR>> targetMappingSupplier,
@NotNull BiFunction<Q,TQ,com.querydsl.core.types.Predicate> correlationPredicateFunction) |
Currently the decision to use `JOIN` is static in the mapping, but it can be more flexible.
|
static <Q extends FlexibleRelationalPathBase<R>,R,TS,TQ extends FlexibleRelationalPathBase<TR>,TR>
TableRelationResolver<Q,R,TS,TQ,TR> |
TableRelationResolver.usingSubquery(@NotNull QueryTableMapping<TS,TQ,TR> targetMapping,
@NotNull BiFunction<Q,TQ,com.querydsl.core.types.Predicate> correlationPredicateFunction) |
|
TableRelationResolver<Q,R,TS,TQ,TR> |
TableRelationResolver.withSubquery() |
|