On Apr 12, 2005, at 10:59 AM, Yonik Seeley wrote:
On Apr 11, 2005, at 5:57 PM, Yonik Seeley wrote:
Erik, why was the last change to BooleanQuery made?
The comment was "Correct BooleanQuery.equals such that every clause
is
compared".
It looks like Vector.equals() should have worked, and the new co
> On Apr 11, 2005, at 5:57 PM, Yonik Seeley wrote:
> > Erik, why was the last change to BooleanQuery made?
> > The comment was "Correct BooleanQuery.equals such that every clause is
> > compared".
> >
> > It looks like Vector.equals() should have worked, and the new code is
> > probably slower as i
On Apr 11, 2005, at 5:57 PM, Yonik Seeley wrote:
Erik, why was the last change to BooleanQuery made?
The comment was "Correct BooleanQuery.equals such that every clause is
compared".
It looks like Vector.equals() should have worked, and the new code is
probably slower as it creates two new arrays.
Erik, why was the last change to BooleanQuery made?
The comment was "Correct BooleanQuery.equals such that every clause is
compared".
It looks like Vector.equals() should have worked, and the new code is
probably slower as it creates two new arrays.
We actually need to do some caching with Query
