Re: [p2-dev] Removing MatchQuery in M7.

[Thomas Watson <tjwatson@xxxxxxxxxx>]

The associated bug report is https://bugs.eclipse.org/bugs/show_bug.cgi?id=307454

Tom



Thomas Hallgren ---03/31/2010 10:19:53 AM---As stated in the deprecation note for MatchQuery, we would like to get

From:	Thomas Hallgren <thomas@xxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	03/31/2010 10:19 AM
Subject:	[p2-dev] Removing MatchQuery in M7.

---

As stated in the deprecation note for MatchQuery, we would like to get 
rid of this class for M7. We are also very anxious not to disrupt our 
clients.

Risks:

Clients may depend on the deprecated class. An alternative solution is 
included in the deprecation note but some code still need to be moved.

Benefits:

1. Tests show that performance is at least a 100 times better when 
indexes are used. A MatchQuery can never use an index.
2. We don't risk queries that have side-effects during evaluation.
3. The _expression_ evaluator can be cleaner if concerns about MatchQuery 
are removed.
4. API is cleaner and easier to elaborate.
5. Queries can be executed by a service in another process (database, 
remote, etc.)
6. No need to expose API for, or document, internal query behavior.

Regards,
Thomas Hallgren

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev