| /plugin/authgoogle/google/contrib/ |
| H A D | Google_CustomsearchService.php | 712 public $queries; variable in Google_Search
748 public function setQueries(Google_Query $queries) { argument
749 $this->queries = $queries;
752 return $this->queries;
|
| /plugin/latexcaption/ |
| H A D | style.less | 87 // Media queries
123 // Media queries
|
| H A D | README.md | 51 …,`w-[40,50,60,70,80]` and can be used in conjunction with optional media queries (`-sm`, `-md`, `-…
|
| /plugin/searchcombinedgoogle/ |
| H A D | README.md | 5 Here we go! This plugin hooks into the DokuWiki search and queries Google for your search word. It …
|
| /plugin/quickstats/lang/en/ |
| H A D | query.txt | 8 …- IP queries (i.e. ip priority) ignore all other fields and if an IP is included in a query where …
38 In the case of output for page queries, there are two results for **accesses**. The one which appe…
41 … appear in every table. The ''Country'' column will be excluded from Country queries. The ''IP''
48 …e you a convenient means of checking names and IP's which you might want to use in your queries. \\
|
| H A D | general_intro.txt | 3 - make specific queries based on country, ip address, and Dokuwiki page names;
|
| /plugin/quickstats/ |
| H A D | README | 1 …oth to a Dokuwiki page and in the admin panel, which can accept detailed queries. Complete detail…
|
| H A D | HOW-TO | 129 There is also an admin panel which has various options for making detailed queries.
|
| /plugin/xcom/lang/en/ |
| H A D | howto.txt | 7 …sult will be a list of all the pages on the remote wiki. Often, however, queries require an id. Fo…
25 …- Some queries may require additional options. Clicking the ''Query types'' button will bring up …
26 …'. See the ''Query types'' listing for details on how to handle array options for specific queries.
28 …- ''Timestamps'': Some queries require a timestamp as a parameter. Xcom will create the timesta…
56 The results of these queries are formatted as tables in which the first column is an action link. I…
58 Action links can also work with queries selected from the drop-down query menu. For more informatio…
|
| /plugin/sqlraw/ |
| H A D | syntax.php | 76 $queries = explode(';', $match);
77 if (trim(end($queries)) == "") {
78 array_pop($queries);
80 return array('sql' => $queries);
|
| /plugin/appendtoquery/ |
| H A D | README | 3 Append a fixed string to all search queries. Can be used to restrict search to a single namespace.
|
| /plugin/sql2wiki/ |
| H A D | README | 3 Save results of sqlite queries into page syntax.
|
| /plugin/tagging/ |
| H A D | helper.php | 127 $queries = array(array('DELETE FROM taggings WHERE pid = ? AND tagger = ?', $id, $user));
129 $queries[] = array('INSERT INTO taggings (pid, tagger, tag, lang) VALUES(?, ?, ?, ?)', $id, $user, $tag, $lang);
132 foreach ($queries as $query) {
|
| /plugin/elasticsearch/vendor/elasticsearch/elasticsearch/docs/ |
| H A D | search-operations.asciidoc | 132 Bool queries can be easily constructed using the client. For example, this
188 queries, so it will be a good demonstration.
|
| H A D | connection-pool.asciidoc | 225 likely loads the client, executes a few queries and then closes. Imagine that
230 In reality, if your script only executes a few queries, the sniffing concept is
|
| H A D | community.asciidoc | 23 Its main goal is to allow for easier structuring of queries and indices in your
|
| /plugin/scrape/ |
| H A D | phpQuery-onefile.php | |
| /plugin/refnotes/lang/en/ |
| H A D | __template.txt | 8 * Store one note per page as [[doku>plugin:data|Data plugin]] entry. This way the notes are stored in a database, which allows to make queries against the bibliography data, for example, see all books of a certain author. Unfortunately Data plugin allows only one ''dataentry'' section per page.
|
| /plugin/authgooglesheets/vendor/google/apiclient-services/src/ |
| H A D | Bigquery.php | 258 'path' => 'projects/{projectId}/queries/{jobId}',
346 'path' => 'projects/{projectId}/queries',
|
| /plugin/elasticsearch/vendor/elasticsearch/elasticsearch/docs/build/Elasticsearch/Namespaces/ |
| H A D | AsyncSearchNamespace.asciidoc | 83 $params['analyze_wildcard'] = (boolean) Specify whether wildcard and prefix queries should be analyzed (default: false)
|
| /plugin/strata/ |
| H A D | manual.txt | 225 Patterns are the basic building block of all queries. They are constructed according to the following format:
236 You can refer to 'the current page' with ''%%[[]]%%''. This can be used to write queries that get information related to the page, but defined on other pages.
395 All variables mentioned will be considered to be relevant, even if they are not displayed. Since the queries use so called 'set semantics', results that are equivalent will be reduced to a single result. This can be prevented by declaring additional variables to be considered; results are only equivalent if all displayed and all considered fields are equal.
544 Types are used with data entry to store data in the correct format. Types with queries are used for handling comparisons, and to determine how the data should be displayed.
565 By default, strata does not disable caching. This can result in pages with queries not updating after you edit data somewhere else.
|
| /plugin/photogallery/phpThumb/ |
| H A D | phpthumb.functions.php | 719 $queries = explode($queryseperator, $parsed_url['query']);
721 foreach ($queries as $key => $query) {
|
| /plugin/elasticsearch/vendor/ruflin/elastica/ |
| H A D | CHANGELOG.md | 413 * Added `typed_keys` support for Search queries [#1603](https://github.com/ruflin/Elastica/pull/1603)
532 - For geo_distance queries, sorting, and aggregations the sloppy_arc option has been removed from the distance_type parameter. [#1369](https://github.com/ruflin/Elastica/pull/1369)
534 - The optimize_bbox parameter has been removed from geo_distance queries. [#1369](https://github.com/ruflin/Elastica/pull/1369)
535 - The disable_coord parameter of the bool and common_terms queries has been removed. If provided, it will be ignored and issue a deprecation warning. [#1369](https://github.com/ruflin/Elastica/pull/1369)
604 - Fix for QueryBuilder version check `\Elastica\QueryBuilder\Version\Version240.php` added all new query types to queries array. [#1266](https://github.com/ruflin/Elastica/pull/1266) [#1269](https://github.com/ruflin/Elastica/pull/1269)
693 - Removing all deprecated filters including tests. Use queries instead.
793 - Added support for terminate_after parameter in search queries [#1168](https://github.com/ruflin/Elastica/pull/1168)
868 - Elastica\Filter\* are deprecated. You can use proper queries instead. Backward compatibility layer provided, but will be removed in next Elastica releases. See https://www.elastic.co/blog/better-query-execution-coming-elasticsearch-2-0 and https://github.com/ruflin/Elastica/issues/1001
1193 - fixed reserved words in queries which composed of upper case letters (Util::replaceBooleanWords) [#722](https://github.com/ruflin/Elastica/issues/722/)
1625 - Add filtered queries t
[all...] |
| /plugin/dwtimeline/ |
| H A D | style.less | 284 /* Media queries - Responsive timeline on screens less than 600px wide */
|
| /plugin/elasticsearch/vendor/elasticsearch/elasticsearch/docs/build/Elasticsearch/ |
| H A D | Client.asciidoc | 167 $params['analyze_wildcard'] = (boolean) Specify whether wildcard and prefix queries should be analyzed (default: false)
234 $params['analyze_wildcard'] = (boolean) Specify whether wildcard and prefix queries should be analyzed (default: false)
342 $params['analyze_wildcard'] = (boolean) Specify whether wildcards and prefix queries in the query string query should be analyzed (default: false)
736 $params['analyze_wildcard'] = (boolean) Specify whether wildcard and prefix queries should be analyzed (default: false)
864 $params['analyze_wildcard'] = (boolean) Specify whether wildcard and prefix queries should be analyzed (default: false)
|