S
Simon L. Prinsloo
Guest
Marian, I disagree. Twice. First of all, this behaviour is well documented and is there by design, so it is not a bug. It is in fact very useful. In some workflows a value will only become available later in a process, but when it does, it needs to be unique. Until then, it is absent and it cannot participate in the index. Secondly, null is not a value, it is the absence of a value. The test null eq null does not "compare" two values, it checks if the value is absent.
Continue reading...
Continue reading...