[Groonga-commit] groonga/groonga.github.com [master] doc en: fix previous wrong commit

Back to archive index

HAYASHI Kentaro null+****@clear*****
Wed Aug 29 10:56:07 JST 2012


HAYASHI Kentaro	2012-08-29 10:56:07 +0900 (Wed, 29 Aug 2012)

  New Revision: f6e00dd9037e76eba4203fa456f97ba6f8573a05
  https://github.com/groonga/groonga.github.com/commit/f6e00dd9037e76eba4203fa456f97ba6f8573a05

  Log:
    doc en: fix previous wrong commit

  Modified files:
    en/_posts/2012-08-29-release.textile

  Modified: en/_posts/2012-08-29-release.textile (+29 -46)
===================================================================
--- en/_posts/2012-08-29-release.textile    2012-08-29 10:53:59 +0900 (c809da5)
+++ en/_posts/2012-08-29-release.textile    2012-08-29 10:56:07 +0900 (be07893)
@@ -2,7 +2,6 @@
 layout: post.en
 title: Groonga 2.0.6 has been released
 description: Groonga 2.0.6 has been released!
-published: false
 ---
 
 h2. Groonga 2.0.6 has been released
@@ -11,74 +10,58 @@ h2. Groonga 2.0.6 has been released
 
 How to install: "Install":/docs/install.html
 
-There are four topics for this release.
+There are three topics for this release.
 
-* Supported near search by @'column *N "word1 word2 ..."'@ in script syntax
-* Improved documents
-* Improved groonga-httpd
-* Improved geo_distance to reduce limitations
+* Supported to search the records which does not contain the specified words
+* Added the documentation about groonga for server use
+* Supported http_rewrite_module for groonga-httpd
 
-h3. Supported near search by @'column *N "word1 word2 ..."'@ in script syntax
+h3. Supported to search the records which does not contain the specified words
 
-groonga has prepared syntax for near search, but it does not work.
+This release began to support searching the records which does not contain the specified words.
 
-The operator does near search with words @'word1 word2 ...'@. Near search searches records that contain the words and the words are appeared in the near distance. 
+You can search the records which does not contain 'tomorrow' by following query: (This example use a table named diaries which has the column named content.)
 
-The unit of near distance is the number of characters in N-gram family tokenizers and the number of words in morphological analysis family tokenizers.
-Near distance is always 10 for now.
+<pre>
+select diaries --match_columns content --query "-tomorrow" --query_flags ALLOW_LEADING_NOT
+</pre>
 
-The syntax for "near search":/docs/reference/grn_expr/script_syntax.html#near-search-operator is @'column *N "word1 word2 ..."'@.
+Note that you must use @--query_flags@ with @ALLOW_LEADING_NOT �� . Don't use @ALLOW_LEADING_NOT@ frequently since it is a heavy processing.
 
-h3. Improved documents
+There is another useful option in @--query_flags �� .
 
-The documentation was updated. We will update the documentation continuously in the future.
+Usually, @--query@ with "title:keywords" parameter is treated as "Search keywords from title column". This is the spec of groonga full-text search.
 
-groonga has "specific syntaxes":/docs/reference/grn_expr/script_syntax.html which specify conditional expressions. It is similar to ECMAScript.
+So, you can not search the records without interpreting the specified keyword. There is a problem if the specified keyword contained ':'.
 
-We improved the description about basic ECMAScript related syntaxes, some literals, specific operators for searching and so on.
+You can specify @'NONE'@ as a parameter of @--query_flags@ option in such a case.
 
-There are a schema definition and sample data with execution example, you can try examples immediately.
+Here is a example to search "todo:":
 
-h3. Improved groonga-httpd
+<pre>
+select diaries --match_columns content --query "todo:" --query_flags NONE
+</pre>
 
-There are two points which improved groonga-httpd functionality.
+There are many parameter with "--query_flags option":/docs/reference/commands/select.html#query-flags .
 
-* groonga-httpd supports to customize base URI prefix
-* groonga-httpd supports multiple databases
+h3. Added the documentation about groonga for server use
 
-First, the functionality of customizing base URI prefix was added to groonga-httpd.
+The documentation was added. We will update the documentation continuously in the future.
 
-There were the limitation which supports only @/d/command?parameter1=value&...@ request form as well as groonga HTTP server.
+This release provides a hint to choice groonga as a full-text search engine for server use.
 
-This release improves the functionality of customizing base URI prefix by adding @groonga_base_path@ directive.
+There are two protocol (GQTP and HTTP) which groonga provides. Also, groonga provides two independent implementation about HTTP protocol.
 
-Now that @groonga-httpd@ accepts not only /d/ prefix request form, but also the others.
+You may be confused what to choose. So, we documented "the comparison table about groonga for server use":/docs/server/http/comparison.html. 
 
-So, utilize @groonga_base_path@, you can customize @groonga-httpd@ to restrict the executable commands which depends authentication.
+h3. Supported http_rewrite_module for groonga-httpd
 
-Here is the example which restricts shutdown command using "groonga_base_path":/docs/reference/executables/groonga-httpd.html#groonga-base-path
+This release began to support PCRE auto detection for groonga-httpd. As a result, http_rewrite_module has been enabled in this release.
 
-Secondly, @groonga-httpd@ supports multiple database.
+See nginx website about "@http_rewrite_module@":http://wiki.nginx.org/HttpRewriteModule details:
 
-There is the limitation that groonga HTTP server can handle only 1 database per process.
+  
 
-This release improves the functionality to be able to handle database per location by using @location@ and @groonga_database@ directive.
-
-Now that @groonga-httpd@ can handle multiple databases as if one data source.
-
-See "configuration-directives":/docs/reference/executables/groonga-httpd.html#configuration-directives about directive and setting details.
-
-h3. Improved geo_distance to reduce limitations
-
-Groonga provides built-in functions which calculates the value of distance between two geo graphical points.
-
-And you can select the method of approximation how to approximate the geographical features within square approximation, spherical approximation or ellipsoid approximation.
-
-There are the limitations that geo_distance can not calculate the value of distance across the meridian, the date line or the equator accurately.
-
-This release partially improves the problem if you use square approximation.
-
-For example, if there are points in southern hemisphere, "geo_distance":/docs/functions/geo_distance.html returns the accurate value of distance even thought the line connecting the two points accorss the boundary.
 
 h3. Conclusion
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index