Ticket #487 (new Improvement)
Opened 3 years ago
Repository could allow query-language extensions
| Reported by: | bruno@… | Owned by: | somebody |
|---|---|---|---|
| Priority: | Minor | Milestone: | |
| Component: | Repository - platform / SPI | Version: | |
| Keywords: | Cc: |
Description
[jira2trac import : issue created on May 25, 2007 11:07:20 AM CEST http://issues.cocoondev.org/browse/DSY-487 ]
It would be interesting if the repository would allow extension components to register new functionality in the query language.
This would make it possible to have extensions that add functionality like comments, popularity tracking, trackback, document rating, ... and still have it possible to search on that information from within the query language. E.g. select some documents and order by rating.
From a high-level view, there are two sorts of integrations possible:
- on the SQL level: assuming extensions store their data in the same SQL database as the repository
This would allow for the most powerful searches.
- merging results in Java: as is currently done with the fulltext search.
Adding support for new output-only (non-search) identifiers would of course be rather trivial.