B-index

A B C D E F G H I K L M N O P Q R S T U V W Z

B

Similar to build, the only difference is that it should use ComparisonStrategy based on TypeManager.compareTo chosen with respect to the given contexts

Generally processing logic looks as below:

KeyValueMatcher works on data holders which can be represented as a bag of key-value pairs
Given textual matching rules representations are defined in terms of target keys and their values
We parse the given rule representation string and extract string keys from it in factory-specific way, for example, if it's SQL rule (like k1 = 1 and (k2 < 2 or k3 in (31, 31)), we can use sql parser for that
Parse target keys from their string representations
Get value type for the target key
Find TypeManager for every value type (see TypeManager.targetType and TypeManager.targetContext), given contexts allow to customize that
Parse value objects from their string representations given in the rule string
Build KeyValueMatcher for the parsed keys, values an operations defined in the given matching rule string. Given ComparisonStrategy is used for that

build(java.lang.Object) - function in tech.harmonysoft.oss.common.string.util.ToStringUtil

Convenient way to build object's string representation where some fields should be excluded (e.g.

A B C D E F G H I K L M N O P Q R S T U V W Z