Aha. Well, this is the same query that caused the NPE (in terms of shape). And, for four out of five cases I run in test cases, it runs lickety-split.
Here's the diff between a fast one and a slow one ... 24c24 < ?root (rex:text|rex:alternateText) "Bongani Khumalo" . --- > ?root (rex:text|rex:alternateText) "Al-Qaida" . 62c62 On Thu, Feb 3, 2011 at 5:55 PM, Andy Seaborne <[email protected]> wrote: > Could you explain the testing issue? The queries are quite long and while > it may be obvious to you, it isn't to me! > > Andy > > On 03/02/11 22:44, Benson Margulies wrote: >> >> Sure. Sorry to transgress. In this case, since the very same query >> (structurally) had very different performance characteristics >> depending on which string was used to match a literal, I jumped to a >> conclusion. In particular, I'm assuming that the nature of OPTIONAL is >> that the 'required' part constrains the second part, I didn't think >> that I was inventing something like that. >
