Features/Plain Query Format: Difference between revisions
No edit summary |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> | <noinclude>{{GoogleTrans-en}}{{TOCright}} | ||
[[Category:Feature Page Incomplete]] | |||
[[Category:FeatureObsoleted|Plain Query Format]]</noinclude> | |||
<!-- All fields on this form are required to be accepted. | <!-- All fields on this form are required to be accepted. | ||
| Line 8: | Line 10: | ||
== Summary == | == Summary == | ||
Provide simple string query format for Datastore find() method to cover all kinds of requests. | Provide a simple string query format for the Datastore find() method to cover all kinds of requests. | ||
== Owner == | == Owner == | ||
| Line 17: | Line 19: | ||
== Current status == | == Current status == | ||
* Targeted release: | * Targeted release: ? | ||
* Last updated: Tue Aug 25 07:59:58 UTC 2009 | * Last updated: Tue Aug 25 07:59:58 UTC 2009 | ||
* Percentage of completion: core part was implemented within [[Version support for datastore/Proposal]] | * Percentage of completion: 90%, core part was implemented within [[Version support for datastore/Proposal]] | ||
== Detailed Description == | == Detailed Description == | ||
Let users create complex queries with all possible terms([http://xapian.org/docs/glossary.html | Let users create complex queries with all possible terms (see Xapian [http://xapian.org/docs/glossary.html glossary]) including system ones. Users can use in query string [[#System prefixes|system]] prefixes and predefined set of [[#Users predefined prefixes|custom]] prefixes. | ||
Prefixes in query string could look like | Prefixes in query string could look like | ||
| Line 29: | Line 31: | ||
<prefix>:"<multi-word-value>" | <prefix>:"<multi-word-value>" | ||
Values for system prefixes, | Values for system prefixes, Sugar fills on its own, i.e., if ''title'' metadata field is ''My activity'', user can type ''title:"My activity"'' in query string to search ''My activity'' substring only within ''title'' fields. | ||
Values for [[#Users predefined prefixes|custom]] prefixes user should place to ''tags'' metadata field in the same form like in query string. | Values for [[#Users predefined prefixes|custom]] prefixes user should place to ''tags'' metadata field in the same form like in query string. | ||
If value is multi worded, any of these | If value is multi-worded, any of these words could be used in query, e.g., ''title:My'' or ''title:activity''. | ||
==== System prefixes ==== | ==== System prefixes ==== | ||
| Line 188: | Line 190: | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
* | * Feature lets users specify exact metadata fields to search for. | ||
== Scope == | == Scope == | ||
| Line 212: | Line 211: | ||
== User Experience == | == User Experience == | ||
* | * feature just expands query dictionary | ||
== Dependencies == | == Dependencies == | ||
| Line 234: | Line 232: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | * See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||