| Summary: | [prov] API - querying unique IU's in a repo | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Susan McCourt <susan> |
| Component: | Incubator | Assignee: | equinox.incubator-inbox <equinox.incubator-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, pascal |
| Version: | 3.4 | ||
| Target Milestone: | 3.4 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 209992 | ||
| Bug Blocks: | |||
|
Description
Susan McCourt
After a lengthy discussion with John and Pascal, we've decided that: - The IQueryable interface needs review and possibly more flexibility, but that is not urgent for M4. - For the UI to get what it needs, it should define an interface like a queryable, but including some of the richer queries it needs such as: * query for the latest version rather than a particular version (this solves the issue of getting unique ID's, also) * query for matching property values (might not be needed if categories are expressed as a capability) * possibly support richer expressions rather than a boolean indicating whether something is an AND or not John will look at IQueryable some other time and we may push some of these UI-defined queries down into IQueryable. This was fixed by the new query API and the LatestIUVersionCollector. |