On Jan 9, 2008 2:52 PM, Ard Schrijvers <[EMAIL PROTECTED]> wrote: > > > I'm referring to Section 6.6.3.3. There is a table on p108 > > (I'm going from v1.0.1, March 2006) with the following SQL / XPATH > > correspondence: > > > > my:title IS NULL <-> not(@my:title) > > Perhaps in sql your perception is the correct one, but in xpath it is > not [not(@mytitle)] means that the attribute should be not present. attr > mytitle="" is not the same as absent obviously. I am not sure wether the > spec is ambiguous in this, perhaps somebody else might elaborate. >
I've narrowed down this change in behaviour a bit. In Jackrabbit 1.3, the 'not()' predicate would match multivalued properties that had an empty array as the value. In 1.4, not() no longer matches such properties. I would guess that 1.4 has the correct behaviour and that we were relying on the incorrect behaviour of 1.3. Might be worth an entry in the release notes for 1.4. Best wishes, Dean.
