jimmer Files

weakJoins support lambda

Jimmer has a very important capability: automatically merging conflicting table joins. This is why developers previously had to implement WeakJoin/KWeakJoin using a explicit class. Jimmer uses the class of the weak join to determine whether different weak joins conflict.

Now, if developing applications for the JVM rather than native, users can opt for lambda-based weak joins. Jimmer will analyze the bytecode of different lambda expressions and compare whether their code logic is equivalent to determine if different weak joins conflict.

Java example

```
table.weakJoin(
    TargetTable.class, // Table type, not entity type!
    (source, target) -> source.name().eq(target.name()
)
```

Kotlin example

```
table.weakJoin(Target::class) {
    source.name eq target.name
}
```

1. RemoteKeyPreProvider

Now, RemoteKeyProvider is provided, it can configurable by RedisValueBInder, RedisHashBinder or RedisCacheCreator(in spring-start) This interface can help you to override redis key prefix more easier, rather than override cache binder class.