Guido Casper wrote:
Unico Hommes wrote:
<snip what="thorough_explanation"/>
Notice the is-defined expression in the where clause. Now in order to optimize your query you should try to let each selected property participate in the where clause. For instance by using is-defined clause like above.
OK, I understand better now. However I believe the performance impact of a missing <is-defined/> is negligible?
Actually no. I have some queries where it is the difference between instantanious result and having to wait up to 10 seconds. It depends on the caching settings as well I guess. Because the default property provider reads the properties from the revision descriptor object and this can mean multiple SQL calls per resource in the result set.
But now concerning the NPE. I know what is causing it and why it wasn't there before I will commit a fix later in the day.
Thanks a lot!!
You're most welcome :-)
-- Unico
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
