What is the general use case of the static handling mode?

[mipo256]

I'm not sure that static null handling is very useful.

As it is described in the docs, the client cannot really specify the property value - it will eventually be null and the corresponding SQL will be generated.

I think, it is safe to assert that the idea of any parameters that generally any tool provides to the client that uses the tool is to modify and alter the behavior of the tool. That is what common sense dictates.

Here, the static handling mode is generally not very useful to the client. Whether or not the client specifies it, the behavior is the same, so that the client is not given any additional degree of freedom here.

I think that the identical behavior can be achieved with the fixed for instance and set to null all the time. So, I'm not really sure what is the typical use case that static null handling mode is going to be very useful and necessary.

[babyfish-ct]

Do you mean the ubiquitous strict declaration of whether properties can be nullable?

If you mean this, then it is because jimmer requires Java developers to think about whether each property can be null, just like Kotlin developers. In fact, the predecessor of jimmer was called kimmer, which is a pure Kotlin project. Now in jimmer, Java and Kotlin APIs share the same core. And for Java developers, this is not a bad thing.

If you mean a specific detail feature, please clearly express which feature it is.