rroonga 3.1.1-x86-mingw32 → 3.1.2-x86-mingw32
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Rakefile +1 -39
- data/bin/grndump +8 -1
- data/doc/text/news.textile +21 -1
- data/ext/groonga/extconf.rb +1 -6
- data/ext/groonga/rb-grn-table.c +20 -0
- data/ext/groonga/rb-grn.h +1 -1
- data/ext/groonga/rb-groonga.c +42 -0
- data/lib/1.9/groonga.so +0 -0
- data/lib/2.0/groonga.so +0 -0
- data/lib/2.1/groonga.so +0 -0
- data/lib/groonga/dumper.rb +7 -3
- data/lib/groonga/record.rb +19 -1
- data/rroonga-build.rb +5 -5
- data/test/test-array.rb +14 -1
- data/test/test-database-dumper.rb +68 -83
- data/test/test-database.rb +1 -1
- data/test/test-double-array-trie.rb +16 -1
- data/test/test-hash.rb +16 -1
- data/test/test-lock-timeout.rb +29 -0
- data/test/test-patricia-trie.rb +16 -1
- data/test/test-record.rb +194 -160
- data/test/test-variable-size-column.rb +1 -1
- data/vendor/local/bin/groonga-benchmark.exe +0 -0
- data/vendor/local/bin/groonga.exe +0 -0
- data/vendor/local/bin/libgroonga-0.dll +0 -0
- data/vendor/local/bin/libmecab-1.dll +0 -0
- data/vendor/local/bin/libmsgpack-3.dll +0 -0
- data/vendor/local/bin/libmsgpackc-2.dll +0 -0
- data/vendor/local/bin/mecab-config +2 -2
- data/vendor/local/bin/mecab.exe +0 -0
- data/vendor/local/etc/groonga/httpd/groonga-httpd.conf +2 -2
- data/vendor/local/include/groonga/groonga.h +15 -1
- data/vendor/local/lib/groonga/plugins/query_expanders/tsv.a +0 -0
- data/vendor/local/lib/groonga/plugins/query_expanders/tsv.dll +0 -0
- data/vendor/local/lib/groonga/plugins/query_expanders/tsv.dll.a +0 -0
- data/vendor/local/lib/groonga/plugins/query_expanders/tsv.la +3 -3
- data/vendor/local/lib/groonga/plugins/suggest/suggest.a +0 -0
- data/vendor/local/lib/groonga/plugins/suggest/suggest.dll +0 -0
- data/vendor/local/lib/groonga/plugins/suggest/suggest.dll.a +0 -0
- data/vendor/local/lib/groonga/plugins/suggest/suggest.la +3 -3
- data/vendor/local/lib/groonga/plugins/table/table.a +0 -0
- data/vendor/local/lib/groonga/plugins/table/table.dll +0 -0
- data/vendor/local/lib/groonga/plugins/table/table.dll.a +0 -0
- data/vendor/local/lib/groonga/plugins/table/table.la +3 -3
- data/vendor/local/lib/groonga/plugins/tokenizers/mecab.a +0 -0
- data/vendor/local/lib/groonga/plugins/tokenizers/mecab.dll +0 -0
- data/vendor/local/lib/groonga/plugins/tokenizers/mecab.dll.a +0 -0
- data/vendor/local/lib/groonga/plugins/tokenizers/mecab.la +3 -3
- data/vendor/local/lib/libgroonga.a +0 -0
- data/vendor/local/lib/libgroonga.dll.a +0 -0
- data/vendor/local/lib/libgroonga.la +3 -3
- data/vendor/local/lib/libmecab.a +0 -0
- data/vendor/local/lib/libmecab.dll.a +0 -0
- data/vendor/local/lib/libmecab.la +1 -1
- data/vendor/local/lib/libmsgpack.a +0 -0
- data/vendor/local/lib/libmsgpack.dll.a +0 -0
- data/vendor/local/lib/libmsgpack.la +1 -1
- data/vendor/local/lib/libmsgpackc.a +0 -0
- data/vendor/local/lib/libmsgpackc.dll.a +0 -0
- data/vendor/local/lib/libmsgpackc.la +1 -1
- data/vendor/local/lib/pkgconfig/groonga.pc +3 -3
- data/vendor/local/libexec/mecab/mecab-cost-train.exe +0 -0
- data/vendor/local/libexec/mecab/mecab-dict-gen.exe +0 -0
- data/vendor/local/libexec/mecab/mecab-dict-index.exe +0 -0
- data/vendor/local/libexec/mecab/mecab-system-eval.exe +0 -0
- data/vendor/local/libexec/mecab/mecab-test-gen.exe +0 -0
- data/vendor/local/sbin/groonga-httpd-restart +1 -1
- data/vendor/local/share/doc/groonga/en/html/.buildinfo +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/characteristic.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/community.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/development.txt +2 -2
- data/vendor/local/share/doc/groonga/en/html/_sources/development/travis-ci.txt +6 -6
- data/vendor/local/share/doc/groonga/en/html/_sources/install/centos.txt +7 -7
- data/vendor/local/share/doc/groonga/en/html/_sources/install/debian.txt +6 -6
- data/vendor/local/share/doc/groonga/en/html/_sources/install/fedora.txt +6 -6
- data/vendor/local/share/doc/groonga/en/html/_sources/install/mac_os_x.txt +3 -3
- data/vendor/local/share/doc/groonga/en/html/_sources/install/others.txt +3 -3
- data/vendor/local/share/doc/groonga/en/html/_sources/install/solaris.txt +4 -4
- data/vendor/local/share/doc/groonga/en/html/_sources/install/ubuntu.txt +10 -10
- data/vendor/local/share/doc/groonga/en/html/_sources/install/windows.txt +10 -9
- data/vendor/local/share/doc/groonga/en/html/_sources/limitations.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/news.txt +32 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/api/global_configurations.txt +49 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/commands/cache_limit.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/executables/grnslap.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/executables/groonga.txt +2 -2
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/edit_distance.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/geo_distance.txt +5 -6
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/geo_in_circle.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/geo_in_rectangle.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/html_untag.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/now.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/rand.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/snippet_html.txt +5 -3
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/grn_expr.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/pseudo_column.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/query_expanders/tsv.txt +1 -1
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/tables.txt +4 -4
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/tuning.txt +2 -2
- data/vendor/local/share/doc/groonga/en/html/_sources/server.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/spec.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/suggest/introduction.txt +2 -2
- data/vendor/local/share/doc/groonga/en/html/_sources/troubleshooting.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/drilldown.txt +1 -0
- data/vendor/local/share/doc/groonga/en/html/_static/basic.css +19 -0
- data/vendor/local/share/doc/groonga/en/html/_static/doctools.js +3 -0
- data/vendor/local/share/doc/groonga/en/html/_static/searchtools.js +2 -2
- data/vendor/local/share/doc/groonga/en/html/characteristic.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/community.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/com.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/cooperation.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/document.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/query.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/release.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/repository.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/development/test.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/documentation.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/documentation/c-api.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/documentation/i18n.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/contribution/report.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/development.html +22 -20
- data/vendor/local/share/doc/groonga/en/html/development/travis-ci.html +26 -24
- data/vendor/local/share/doc/groonga/en/html/genindex.html +269 -183
- data/vendor/local/share/doc/groonga/en/html/geolocation_search.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/index.html +41 -38
- data/vendor/local/share/doc/groonga/en/html/install.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/install/centos.html +27 -25
- data/vendor/local/share/doc/groonga/en/html/install/debian.html +26 -24
- data/vendor/local/share/doc/groonga/en/html/install/fedora.html +26 -24
- data/vendor/local/share/doc/groonga/en/html/install/mac_os_x.html +23 -21
- data/vendor/local/share/doc/groonga/en/html/install/others.html +23 -21
- data/vendor/local/share/doc/groonga/en/html/install/solaris.html +24 -22
- data/vendor/local/share/doc/groonga/en/html/install/ubuntu.html +30 -28
- data/vendor/local/share/doc/groonga/en/html/install/windows.html +29 -27
- data/vendor/local/share/doc/groonga/en/html/limitations.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/news.html +239 -201
- data/vendor/local/share/doc/groonga/en/html/news/0.x.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/news/1.0.x.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/news/1.1.x.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/news/1.2.x.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/news/senna.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/objects.inv +0 -0
- data/vendor/local/share/doc/groonga/en/html/reference.html +41 -38
- data/vendor/local/share/doc/groonga/en/html/reference/api.html +46 -43
- data/vendor/local/share/doc/groonga/en/html/reference/api/global_configurations.html +205 -0
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_cache.html +55 -53
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_column.html +78 -76
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_command_version.html +48 -46
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_ctx.html +75 -73
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_db.html +54 -52
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_encoding.html +46 -44
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_expr.html +62 -60
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_geo.html +46 -44
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_hook.html +46 -44
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_ii.html +48 -46
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_index_cursor.html +42 -40
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_info.html +46 -44
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_match_escalation.html +44 -42
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_obj.html +117 -115
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_proc.html +48 -46
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_search.html +40 -38
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_table.html +80 -78
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_table_cursor.html +56 -54
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_type.html +40 -38
- data/vendor/local/share/doc/groonga/en/html/reference/api/grn_user_data.html +36 -34
- data/vendor/local/share/doc/groonga/en/html/reference/cast.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/command.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/command/command_version.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/command/output_format.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/command/return_code.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/cache_limit.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/check.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/clearlock.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/column_create.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/column_list.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/column_remove.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/column_rename.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/define_selector.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/defrag.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/delete.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/dump.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/load.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/log_level.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/log_put.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/log_reopen.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/normalize.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/quit.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/register.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/ruby_eval.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/ruby_load.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/select.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/shutdown.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/status.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/suggest.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/table_create.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/table_list.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/commands/table_remove.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/tokenize.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/commands/truncate.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/executables.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/executables/grnslap.html +23 -21
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-benchmark.html +26 -24
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-httpd.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-server-http.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-suggest-create-dataset.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-suggest-httpd.html +26 -24
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga-suggest-learner.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/executables/groonga.html +33 -31
- data/vendor/local/share/doc/groonga/en/html/reference/function.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/functions/between.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/functions/edit_distance.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/geo_distance.html +23 -21
- data/vendor/local/share/doc/groonga/en/html/reference/functions/geo_in_circle.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/geo_in_rectangle.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/html_untag.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/now.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/query.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/functions/rand.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/functions/snippet_html.html +24 -21
- data/vendor/local/share/doc/groonga/en/html/reference/functions/sub_filter.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/grn_expr.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/grn_expr/query_syntax.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/grn_expr/script_syntax.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/indexing.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/log.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/normalizers.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/output.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/pseudo_column.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/query_expanders.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/query_expanders/tsv.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/reference/tables.html +24 -22
- data/vendor/local/share/doc/groonga/en/html/reference/tokenizers.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/reference/tuning.html +22 -20
- data/vendor/local/share/doc/groonga/en/html/reference/types.html +21 -19
- data/vendor/local/share/doc/groonga/en/html/search.html +12 -12
- data/vendor/local/share/doc/groonga/en/html/searchindex.js +1 -1
- data/vendor/local/share/doc/groonga/en/html/server.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/gqtp.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/http.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/http/comparison.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/http/groonga-httpd.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/http/groonga.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/server/package.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/spec.html +24 -22
- data/vendor/local/share/doc/groonga/en/html/spec/gqtp.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/spec/search.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/suggest.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/suggest/completion.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/suggest/correction.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/suggest/introduction.html +22 -20
- data/vendor/local/share/doc/groonga/en/html/suggest/suggestion.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/suggest/tutorial.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/troubleshooting.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/troubleshooting/different_results_with_the_same_keyword.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/troubleshooting/mmap_cannot_allocate_memory.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/data.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/drilldown.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/index.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/introduction.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/lexicon.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/match_columns.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/micro_blog.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/network.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/patricia_trie.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/query_expansion.html +20 -18
- data/vendor/local/share/doc/groonga/en/html/tutorial/search.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/.buildinfo +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/characteristic.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/community.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/development.txt +2 -2
- data/vendor/local/share/doc/groonga/ja/html/_sources/development/travis-ci.txt +6 -6
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/centos.txt +7 -7
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/debian.txt +6 -6
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/fedora.txt +6 -6
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/mac_os_x.txt +3 -3
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/others.txt +3 -3
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/solaris.txt +4 -4
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/ubuntu.txt +10 -10
- data/vendor/local/share/doc/groonga/ja/html/_sources/install/windows.txt +10 -9
- data/vendor/local/share/doc/groonga/ja/html/_sources/limitations.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/news.txt +32 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/api/global_configurations.txt +49 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/cache_limit.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/executables/grnslap.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/executables/groonga.txt +2 -2
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/edit_distance.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/geo_distance.txt +5 -6
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/geo_in_circle.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/geo_in_rectangle.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/html_untag.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/now.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/rand.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/functions/snippet_html.txt +5 -3
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/grn_expr.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/pseudo_column.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/query_expanders/tsv.txt +1 -1
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/tables.txt +4 -4
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/tuning.txt +2 -2
- data/vendor/local/share/doc/groonga/ja/html/_sources/server.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/spec.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/suggest/introduction.txt +2 -2
- data/vendor/local/share/doc/groonga/ja/html/_sources/troubleshooting.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/drilldown.txt +1 -0
- data/vendor/local/share/doc/groonga/ja/html/_static/basic.css +19 -0
- data/vendor/local/share/doc/groonga/ja/html/_static/doctools.js +3 -0
- data/vendor/local/share/doc/groonga/ja/html/_static/searchtools.js +2 -2
- data/vendor/local/share/doc/groonga/ja/html/characteristic.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/community.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/com.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/cooperation.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/document.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/query.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/release.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/repository.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/development/test.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/documentation.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/documentation/c-api.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/documentation/i18n.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/contribution/report.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/development.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/development/travis-ci.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/genindex.html +274 -183
- data/vendor/local/share/doc/groonga/ja/html/geolocation_search.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/index.html +41 -38
- data/vendor/local/share/doc/groonga/ja/html/install.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/install/centos.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/debian.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/fedora.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/mac_os_x.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/others.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/solaris.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/ubuntu.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/install/windows.html +29 -27
- data/vendor/local/share/doc/groonga/ja/html/limitations.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/news.html +264 -224
- data/vendor/local/share/doc/groonga/ja/html/news/0.x.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/news/1.0.x.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/news/1.1.x.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/news/1.2.x.html +27 -25
- data/vendor/local/share/doc/groonga/ja/html/news/senna.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/objects.inv +0 -0
- data/vendor/local/share/doc/groonga/ja/html/reference.html +41 -38
- data/vendor/local/share/doc/groonga/ja/html/reference/api.html +46 -43
- data/vendor/local/share/doc/groonga/ja/html/reference/api/global_configurations.html +206 -0
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_cache.html +55 -53
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_column.html +78 -76
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_command_version.html +48 -46
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_ctx.html +74 -72
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_db.html +54 -52
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_encoding.html +46 -44
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_expr.html +62 -60
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_geo.html +46 -44
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_hook.html +46 -44
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_ii.html +48 -46
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_index_cursor.html +42 -40
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_info.html +46 -44
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_match_escalation.html +44 -42
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_obj.html +117 -115
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_proc.html +48 -46
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_search.html +40 -38
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_table.html +80 -78
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_table_cursor.html +56 -54
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_type.html +40 -38
- data/vendor/local/share/doc/groonga/ja/html/reference/api/grn_user_data.html +36 -34
- data/vendor/local/share/doc/groonga/ja/html/reference/cast.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/command.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/command/command_version.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/command/output_format.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/command/return_code.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/cache_limit.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/check.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/clearlock.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/column_create.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/column_list.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/column_remove.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/column_rename.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/define_selector.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/defrag.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/delete.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/dump.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/load.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/log_level.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/log_put.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/log_reopen.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/normalize.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/quit.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/register.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/ruby_eval.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/ruby_load.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/select.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/shutdown.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/status.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/suggest.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/table_create.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/table_list.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/table_remove.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/tokenize.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/commands/truncate.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/executables.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/grnslap.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-benchmark.html +26 -24
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-httpd.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-server-http.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-suggest-create-dataset.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-suggest-httpd.html +26 -24
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga-suggest-learner.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/executables/groonga.html +33 -31
- data/vendor/local/share/doc/groonga/ja/html/reference/function.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/between.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/edit_distance.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/geo_distance.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/geo_in_circle.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/geo_in_rectangle.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/html_untag.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/now.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/query.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/rand.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/snippet_html.html +24 -20
- data/vendor/local/share/doc/groonga/ja/html/reference/functions/sub_filter.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/grn_expr.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/reference/grn_expr/query_syntax.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/grn_expr/script_syntax.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/indexing.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/reference/log.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/normalizers.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/output.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/reference/pseudo_column.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/query_expanders.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/query_expanders/tsv.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/reference/tables.html +23 -21
- data/vendor/local/share/doc/groonga/ja/html/reference/tokenizers.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/reference/tuning.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/reference/types.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/search.html +12 -12
- data/vendor/local/share/doc/groonga/ja/html/searchindex.js +1 -1
- data/vendor/local/share/doc/groonga/ja/html/server.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/gqtp.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/http.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/http/comparison.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/http/groonga-httpd.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/http/groonga.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/server/package.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/spec.html +24 -22
- data/vendor/local/share/doc/groonga/ja/html/spec/gqtp.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/spec/search.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/suggest.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/suggest/completion.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/suggest/correction.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/suggest/introduction.html +21 -19
- data/vendor/local/share/doc/groonga/ja/html/suggest/suggestion.html +22 -20
- data/vendor/local/share/doc/groonga/ja/html/suggest/tutorial.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/troubleshooting.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/troubleshooting/different_results_with_the_same_keyword.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/troubleshooting/mmap_cannot_allocate_memory.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/data.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/drilldown.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/index.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/introduction.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/lexicon.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/match_columns.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/micro_blog.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/network.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/patricia_trie.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/query_expansion.html +20 -18
- data/vendor/local/share/doc/groonga/ja/html/tutorial/search.html +20 -18
- data/vendor/local/share/man/ja/man1/groonga.1 +198 -132
- data/vendor/local/share/man/man1/groonga.1 +619 -554
- metadata +8 -14
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/commands_not_implemented/add.txt +0 -104
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/commands_not_implemented/get.txt +0 -80
- data/vendor/local/share/doc/groonga/en/html/_sources/reference/commands_not_implemented/set.txt +0 -105
- data/vendor/local/share/doc/groonga/en/html/reference/commands_not_implemented/add.html +0 -199
- data/vendor/local/share/doc/groonga/en/html/reference/commands_not_implemented/get.html +0 -180
- data/vendor/local/share/doc/groonga/en/html/reference/commands_not_implemented/set.html +0 -201
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands_not_implemented/add.txt +0 -104
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands_not_implemented/get.txt +0 -80
- data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands_not_implemented/set.txt +0 -105
- data/vendor/local/share/doc/groonga/ja/html/reference/commands_not_implemented/add.html +0 -200
- data/vendor/local/share/doc/groonga/ja/html/reference/commands_not_implemented/get.html +0 -181
- data/vendor/local/share/doc/groonga/ja/html/reference/commands_not_implemented/set.html +0 -202
@@ -1,4 +1,6 @@
|
|
1
|
-
|
1
|
+
.\" Man page generated from reStructuredText.
|
2
|
+
.
|
3
|
+
.TH "GROONGA" "1" "January 27, 2014" "3.1.2" "Groonga"
|
2
4
|
.SH NAME
|
3
5
|
groonga \- Groonga documentation
|
4
6
|
.
|
@@ -28,8 +30,6 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
|
|
28
30
|
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
|
29
31
|
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
|
30
32
|
..
|
31
|
-
.\" Man page generated from reStructuredText.
|
32
|
-
.
|
33
33
|
.INDENT 0.0
|
34
34
|
.IP \(bu 2
|
35
35
|
\fBnews\fP
|
@@ -41,7 +41,7 @@ Groonga is a fast and accurate full text search engine based on inverted index.
|
|
41
41
|
.sp
|
42
42
|
Groonga is also a column\-oriented database management system (DBMS). Compared with well\-known row\-oriented systems, such as MySQL and PostgreSQL, column\-oriented systems are more suited for aggregate queries. Due to this advantage, Groonga can cover weakness of row\-oriented systems.
|
43
43
|
.sp
|
44
|
-
The basic functions of Groonga are provided in a C library. Also, libraries for using Groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga\-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use Groonga. See \fI\%usage examples\fP
|
44
|
+
The basic functions of Groonga are provided in a C library. Also, libraries for using Groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga\-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use Groonga. See \fI\%usage examples\fP\&.
|
45
45
|
.SS Full text search and Instant update
|
46
46
|
.sp
|
47
47
|
In widely used DBMSs, updates are immediately processed, for example, a newly registered record appears in the result of the next query. In contrast, some full text search engines do not support instant updates, because it is difficult to dynamically update inverted indexes, the underlying data structure.
|
@@ -110,7 +110,7 @@ packages.groonga.org:
|
|
110
110
|
.INDENT 3.5
|
111
111
|
.INDENT 0.0
|
112
112
|
.IP \(bu 2
|
113
|
-
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.
|
113
|
+
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x86.exe\fP
|
114
114
|
.UNINDENT
|
115
115
|
.UNINDENT
|
116
116
|
.UNINDENT
|
@@ -123,7 +123,7 @@ packages.goronga.org:
|
|
123
123
|
.INDENT 3.5
|
124
124
|
.INDENT 0.0
|
125
125
|
.IP \(bu 2
|
126
|
-
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.
|
126
|
+
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x64.exe\fP
|
127
127
|
.UNINDENT
|
128
128
|
.UNINDENT
|
129
129
|
.UNINDENT
|
@@ -131,7 +131,7 @@ packages.goronga.org:
|
|
131
131
|
Then run it.
|
132
132
|
.sp
|
133
133
|
Use command prompt in start menu to run
|
134
|
-
\fB/reference/executables/groonga\fP
|
134
|
+
\fB/reference/executables/groonga\fP\&.
|
135
135
|
.SS zip
|
136
136
|
.sp
|
137
137
|
For 32\-bit environment, download x86 zip archive from
|
@@ -140,7 +140,7 @@ packages.groonga.org:
|
|
140
140
|
.INDENT 3.5
|
141
141
|
.INDENT 0.0
|
142
142
|
.IP \(bu 2
|
143
|
-
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.
|
143
|
+
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x86.zip\fP
|
144
144
|
.UNINDENT
|
145
145
|
.UNINDENT
|
146
146
|
.UNINDENT
|
@@ -153,7 +153,7 @@ packages.groonga.org:
|
|
153
153
|
.INDENT 3.5
|
154
154
|
.INDENT 0.0
|
155
155
|
.IP \(bu 2
|
156
|
-
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.
|
156
|
+
\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x64.zip\fP
|
157
157
|
.UNINDENT
|
158
158
|
.UNINDENT
|
159
159
|
.UNINDENT
|
@@ -181,7 +181,7 @@ Download zipped source from packages.groonga.org:
|
|
181
181
|
.INDENT 3.5
|
182
182
|
.INDENT 0.0
|
183
183
|
.IP \(bu 2
|
184
|
-
\fI\%http://packages.groonga.org/source/groonga/groonga\-3.1.
|
184
|
+
\fI\%http://packages.groonga.org/source/groonga/groonga\-3.1.2.zip\fP
|
185
185
|
.UNINDENT
|
186
186
|
.UNINDENT
|
187
187
|
.UNINDENT
|
@@ -194,13 +194,13 @@ Move to the Groonga\(aqs source folder:
|
|
194
194
|
.sp
|
195
195
|
.nf
|
196
196
|
.ft C
|
197
|
-
> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.1.
|
197
|
+
> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.1.2
|
198
198
|
.ft P
|
199
199
|
.fi
|
200
200
|
.UNINDENT
|
201
201
|
.UNINDENT
|
202
202
|
.sp
|
203
|
-
Configure by \fBcmake\fP
|
203
|
+
Configure by \fBcmake\fP\&. The following commnad line is for 64\-bit
|
204
204
|
version. To build 32\-bit version, use \fB\-G "Visual Studio 10"\fP
|
205
205
|
parameter instead:
|
206
206
|
.INDENT 0.0
|
@@ -208,7 +208,7 @@ parameter instead:
|
|
208
208
|
.sp
|
209
209
|
.nf
|
210
210
|
.ft C
|
211
|
-
groonga\-3.1.
|
211
|
+
groonga\-3.1.2> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
|
212
212
|
.ft P
|
213
213
|
.fi
|
214
214
|
.UNINDENT
|
@@ -220,7 +220,7 @@ Build:
|
|
220
220
|
.sp
|
221
221
|
.nf
|
222
222
|
.ft C
|
223
|
-
groonga\-3.1.
|
223
|
+
groonga\-3.1.2> cmake \-\-build . \-\-config Release
|
224
224
|
.ft P
|
225
225
|
.fi
|
226
226
|
.UNINDENT
|
@@ -232,18 +232,18 @@ Install:
|
|
232
232
|
.sp
|
233
233
|
.nf
|
234
234
|
.ft C
|
235
|
-
groonga\-3.1.
|
235
|
+
groonga\-3.1.2> cmake \-\-build . \-\-config Release \-\-target Install
|
236
236
|
.ft P
|
237
237
|
.fi
|
238
238
|
.UNINDENT
|
239
239
|
.UNINDENT
|
240
240
|
.sp
|
241
241
|
After the above steps, \fB/reference/executables/groonga\fP is found in
|
242
|
-
\fBc:\egroonga\ebin\egroonga.exe\fP
|
242
|
+
\fBc:\egroonga\ebin\egroonga.exe\fP\&.
|
243
243
|
.SS Mac OS X
|
244
244
|
.sp
|
245
245
|
This section describes how to install groonga on Mac OS X. You can
|
246
|
-
install groonga by \fI\%MacPorts\fP or \fI\%Homebrew\fP
|
246
|
+
install groonga by \fI\%MacPorts\fP or \fI\%Homebrew\fP\&.
|
247
247
|
.sp
|
248
248
|
We distribute both 32\-bit and 64\-bit packages but we strongly
|
249
249
|
recommend a 64\-bit package for server. You should use a 32\-bit package
|
@@ -278,7 +278,7 @@ Install:
|
|
278
278
|
.UNINDENT
|
279
279
|
.SS Build from source
|
280
280
|
.sp
|
281
|
-
Install \fI\%Xcode\fP
|
281
|
+
Install \fI\%Xcode\fP\&.
|
282
282
|
.sp
|
283
283
|
Download source:
|
284
284
|
.INDENT 0.0
|
@@ -286,9 +286,9 @@ Download source:
|
|
286
286
|
.sp
|
287
287
|
.nf
|
288
288
|
.ft C
|
289
|
-
% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.1.
|
290
|
-
% tar xvzf groonga\-3.1.
|
291
|
-
% cd groonga\-3.1.
|
289
|
+
% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
290
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
291
|
+
% cd groonga\-3.1.2
|
292
292
|
.ft P
|
293
293
|
.fi
|
294
294
|
.UNINDENT
|
@@ -331,8 +331,8 @@ Install:
|
|
331
331
|
.UNINDENT
|
332
332
|
.SS Debian GNU/Linux
|
333
333
|
.sp
|
334
|
-
This section describes how to install
|
335
|
-
Debian GNU/Linux. You can install them by \fBapt\fP
|
334
|
+
This section describes how to install Groonga related deb packages on
|
335
|
+
Debian GNU/Linux. You can install them by \fBapt\fP\&.
|
336
336
|
.sp
|
337
337
|
We distribute both 32\-bit and 64\-bit packages but we strongly
|
338
338
|
recommend a 64\-bit package for server. You should use a 32\-bit package
|
@@ -362,7 +362,7 @@ See \fB/server\fP section about details.
|
|
362
362
|
.UNINDENT
|
363
363
|
.SS wheezy
|
364
364
|
.sp
|
365
|
-
Add the
|
365
|
+
Add the Groonga apt repository.
|
366
366
|
.sp
|
367
367
|
/etc/apt/sources.list.d/groonga.list:
|
368
368
|
.INDENT 0.0
|
@@ -500,7 +500,7 @@ Install groonga\-munin\-plugins package:
|
|
500
500
|
.UNINDENT
|
501
501
|
.sp
|
502
502
|
There is a package that provides MySQL compatible normalizer as
|
503
|
-
|
503
|
+
Groonga plugins.
|
504
504
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
505
505
|
.sp
|
506
506
|
Install groonga\-normalizer\-mysql package:
|
@@ -611,9 +611,9 @@ Download source:
|
|
611
611
|
.sp
|
612
612
|
.nf
|
613
613
|
.ft C
|
614
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
615
|
-
% tar xvzf groonga\-3.1.
|
616
|
-
% cd groonga\-3.1.
|
614
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
615
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
616
|
+
% cd groonga\-3.1.2
|
617
617
|
.ft P
|
618
618
|
.fi
|
619
619
|
.UNINDENT
|
@@ -656,8 +656,8 @@ Install:
|
|
656
656
|
.UNINDENT
|
657
657
|
.SS Ubuntu
|
658
658
|
.sp
|
659
|
-
This section describes how to install
|
660
|
-
Ubuntu. You can install them by \fBapt\fP
|
659
|
+
This section describes how to install Groonga related deb packages on
|
660
|
+
Ubuntu. You can install them by \fBapt\fP\&.
|
661
661
|
.sp
|
662
662
|
We distribute both 32\-bit and 64\-bit packages but we strongly
|
663
663
|
recommend a 64\-bit package for server. You should use a 32\-bit package
|
@@ -705,7 +705,7 @@ Enable the universe repository to install groonga:
|
|
705
705
|
.UNINDENT
|
706
706
|
.UNINDENT
|
707
707
|
.sp
|
708
|
-
Add the
|
708
|
+
Add the Groonga apt repository.
|
709
709
|
.sp
|
710
710
|
/etc/apt/sources.list.d/groonga.list:
|
711
711
|
.INDENT 0.0
|
@@ -766,7 +766,7 @@ Install groonga\-munin\-plugins package:
|
|
766
766
|
.UNINDENT
|
767
767
|
.sp
|
768
768
|
There is a package that provides MySQL compatible normalizer as
|
769
|
-
|
769
|
+
Groonga plugins.
|
770
770
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
771
771
|
.sp
|
772
772
|
Install groonga\-normalizer\-mysql package:
|
@@ -800,7 +800,7 @@ Enable the universe repository to install groonga:
|
|
800
800
|
.UNINDENT
|
801
801
|
.UNINDENT
|
802
802
|
.sp
|
803
|
-
Add the
|
803
|
+
Add the Groonga apt repository.
|
804
804
|
.sp
|
805
805
|
/etc/apt/sources.list.d/groonga.list:
|
806
806
|
.INDENT 0.0
|
@@ -846,7 +846,7 @@ Install groonga\-tokenizer\-mecab package:
|
|
846
846
|
.UNINDENT
|
847
847
|
.sp
|
848
848
|
There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
|
849
|
-
|
849
|
+
Groonga status by Munin, install groonga\-munin\-plugins package.
|
850
850
|
.sp
|
851
851
|
Install groonga\-munin\-plugins package:
|
852
852
|
.INDENT 0.0
|
@@ -861,7 +861,7 @@ Install groonga\-munin\-plugins package:
|
|
861
861
|
.UNINDENT
|
862
862
|
.sp
|
863
863
|
There is a package that provides MySQL compatible normalizer as
|
864
|
-
|
864
|
+
Groonga plugins.
|
865
865
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
866
866
|
.sp
|
867
867
|
Install groonga\-normalizer\-mysql package:
|
@@ -895,7 +895,7 @@ Enable the universe repository to install groonga:
|
|
895
895
|
.UNINDENT
|
896
896
|
.UNINDENT
|
897
897
|
.sp
|
898
|
-
Add the
|
898
|
+
Add the Groonga apt repository.
|
899
899
|
.sp
|
900
900
|
/etc/apt/sources.list.d/groonga.list:
|
901
901
|
.INDENT 0.0
|
@@ -1067,9 +1067,9 @@ Download source:
|
|
1067
1067
|
.sp
|
1068
1068
|
.nf
|
1069
1069
|
.ft C
|
1070
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
1071
|
-
% tar xvzf groonga\-3.1.
|
1072
|
-
% cd groonga\-3.1.
|
1070
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
1071
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
1072
|
+
% cd groonga\-3.1.2
|
1073
1073
|
.ft P
|
1074
1074
|
.fi
|
1075
1075
|
.UNINDENT
|
@@ -1113,7 +1113,7 @@ Install:
|
|
1113
1113
|
.SS CentOS
|
1114
1114
|
.sp
|
1115
1115
|
This section describes how to install groonga related RPM packages on
|
1116
|
-
CentOS. You can install them by \fByum\fP
|
1116
|
+
CentOS. You can install them by \fByum\fP\&.
|
1117
1117
|
.sp
|
1118
1118
|
We distribute both 32\-bit and 64\-bit packages but we strongly
|
1119
1119
|
recommend a 64\-bit package for server. You should use a 32\-bit package
|
@@ -1199,7 +1199,7 @@ Or install Juman dictionary:
|
|
1199
1199
|
.UNINDENT
|
1200
1200
|
.sp
|
1201
1201
|
There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
|
1202
|
-
|
1202
|
+
Groonga status by Munin, install groonga\-munin\-plugins package.
|
1203
1203
|
.sp
|
1204
1204
|
\fBNOTE:\fP
|
1205
1205
|
.INDENT 0.0
|
@@ -1208,7 +1208,7 @@ Groonga\-munin\-plugins package requires munin\-node package that
|
|
1208
1208
|
isn\(aqt included in the official CentOS repository. You need to
|
1209
1209
|
enable \fI\%Repoforge (RPMforge)\fP repository
|
1210
1210
|
or \fI\%EPEL\fP repository to
|
1211
|
-
install it by \fByum\fP
|
1211
|
+
install it by \fByum\fP\&.
|
1212
1212
|
.sp
|
1213
1213
|
Enable Repoforge (RPMforge) repository on i386 environment:
|
1214
1214
|
.INDENT 0.0
|
@@ -1264,7 +1264,7 @@ Install groonga\-munin\-plugins package:
|
|
1264
1264
|
.UNINDENT
|
1265
1265
|
.sp
|
1266
1266
|
There is a package that provides MySQL compatible normalizer as
|
1267
|
-
|
1267
|
+
Groonga plugins.
|
1268
1268
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
1269
1269
|
.sp
|
1270
1270
|
Install groonga\-normalizer\-mysql package:
|
@@ -1336,7 +1336,7 @@ Or install Juman dictionary:
|
|
1336
1336
|
.UNINDENT
|
1337
1337
|
.sp
|
1338
1338
|
There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
|
1339
|
-
|
1339
|
+
Groonga status by Munin, install groonga\-munin\-plugins package.
|
1340
1340
|
.sp
|
1341
1341
|
\fBNOTE:\fP
|
1342
1342
|
.INDENT 0.0
|
@@ -1344,7 +1344,7 @@ groonga status by Munin, install groonga\-munin\-plugins package.
|
|
1344
1344
|
Groonga\-munin\-plugins package requires munin\-node package that
|
1345
1345
|
isn\(aqt included in the official CentOS repository. You need to
|
1346
1346
|
enable \fI\%EPEL\fP repository to
|
1347
|
-
install it by \fByum\fP
|
1347
|
+
install it by \fByum\fP\&.
|
1348
1348
|
.sp
|
1349
1349
|
Enable EPEL repository on any environment:
|
1350
1350
|
.INDENT 0.0
|
@@ -1373,7 +1373,7 @@ Install groonga\-munin\-plugins package:
|
|
1373
1373
|
.UNINDENT
|
1374
1374
|
.sp
|
1375
1375
|
There is a package that provides MySQL compatible normalizer as
|
1376
|
-
|
1376
|
+
Groonga plugins.
|
1377
1377
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
1378
1378
|
.sp
|
1379
1379
|
Install groonga\-normalizer\-mysql package:
|
@@ -1407,9 +1407,9 @@ Download source:
|
|
1407
1407
|
.sp
|
1408
1408
|
.nf
|
1409
1409
|
.ft C
|
1410
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
1411
|
-
% tar xvzf groonga\-3.1.
|
1412
|
-
% cd groonga\-3.1.
|
1410
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
1411
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
1412
|
+
% cd groonga\-3.1.2
|
1413
1413
|
.ft P
|
1414
1414
|
.fi
|
1415
1415
|
.UNINDENT
|
@@ -1453,12 +1453,12 @@ Install:
|
|
1453
1453
|
.SS Fedora
|
1454
1454
|
.sp
|
1455
1455
|
This section describes how to install groonga related RPM packages on
|
1456
|
-
Fedora. You can install them by \fByum\fP
|
1456
|
+
Fedora. You can install them by \fByum\fP\&.
|
1457
1457
|
.sp
|
1458
1458
|
\fBNOTE:\fP
|
1459
1459
|
.INDENT 0.0
|
1460
1460
|
.INDENT 3.5
|
1461
|
-
Since
|
1461
|
+
Since Groonga 3.0.2 release, Groonga related RPM pakcages are in the official
|
1462
1462
|
Fedora yum repository (Fedora 18). So you can use them instead of the groonga yum
|
1463
1463
|
repository now. There is some exceptions to use the groonga yum
|
1464
1464
|
repository because \fBgroonga\-normalizer\-mysql\fP and mecab dictionaries
|
@@ -1565,7 +1565,7 @@ Or install Juman dictionary:
|
|
1565
1565
|
.UNINDENT
|
1566
1566
|
.sp
|
1567
1567
|
There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
|
1568
|
-
|
1568
|
+
Groonga status by Munin, install groonga\-munin\-plugins package.
|
1569
1569
|
.sp
|
1570
1570
|
Install groonga\-munin\-plugins package:
|
1571
1571
|
.INDENT 0.0
|
@@ -1580,7 +1580,7 @@ Install groonga\-munin\-plugins package:
|
|
1580
1580
|
.UNINDENT
|
1581
1581
|
.sp
|
1582
1582
|
There is a package that provides MySQL compatible normalizer as
|
1583
|
-
|
1583
|
+
Groonga plugins.
|
1584
1584
|
If you want to use that one, install groonga\-normalizer\-mysql package.
|
1585
1585
|
.sp
|
1586
1586
|
Install groonga\-normalizer\-mysql package:
|
@@ -1614,9 +1614,9 @@ Download source:
|
|
1614
1614
|
.sp
|
1615
1615
|
.nf
|
1616
1616
|
.ft C
|
1617
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
1618
|
-
% tar xvzf groonga\-3.1.
|
1619
|
-
% cd groonga\-3.1.
|
1617
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
1618
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
1619
|
+
% cd groonga\-3.1.2
|
1620
1620
|
.ft P
|
1621
1621
|
.fi
|
1622
1622
|
.UNINDENT
|
@@ -1659,7 +1659,7 @@ Install:
|
|
1659
1659
|
.UNINDENT
|
1660
1660
|
.SS Oracle Solaris
|
1661
1661
|
.sp
|
1662
|
-
This section describes how to install
|
1662
|
+
This section describes how to install Groonga from source on Oracle
|
1663
1663
|
Solaris.
|
1664
1664
|
.SS Oracle Solaris 11
|
1665
1665
|
.sp
|
@@ -1681,9 +1681,9 @@ Download source:
|
|
1681
1681
|
.sp
|
1682
1682
|
.nf
|
1683
1683
|
.ft C
|
1684
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
1685
|
-
% gtar xvzf groonga\-3.1.
|
1686
|
-
% cd groonga\-3.1.
|
1684
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
1685
|
+
% gtar xvzf groonga\-3.1.2.tar.gz
|
1686
|
+
% cd groonga\-3.1.2
|
1687
1687
|
.ft P
|
1688
1688
|
.fi
|
1689
1689
|
.UNINDENT
|
@@ -1734,7 +1734,7 @@ environment.
|
|
1734
1734
|
.sp
|
1735
1735
|
To get more detail about installing groonga from source on the
|
1736
1736
|
specific environment, find the document for the specific environment
|
1737
|
-
from \fB/install\fP
|
1737
|
+
from \fB/install\fP\&.
|
1738
1738
|
.SS Dependencies
|
1739
1739
|
.sp
|
1740
1740
|
Groonga doesn\(aqt require any special libraries but requires some tools
|
@@ -1823,9 +1823,9 @@ steps:
|
|
1823
1823
|
.sp
|
1824
1824
|
.nf
|
1825
1825
|
.ft C
|
1826
|
-
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.
|
1827
|
-
% tar xvzf groonga\-3.1.
|
1828
|
-
% cd groonga\-3.1.
|
1826
|
+
% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
|
1827
|
+
% tar xvzf groonga\-3.1.2.tar.gz
|
1828
|
+
% cd groonga\-3.1.2
|
1829
1829
|
% ./configure
|
1830
1830
|
% make
|
1831
1831
|
% sudo make install
|
@@ -1835,7 +1835,7 @@ steps:
|
|
1835
1835
|
.UNINDENT
|
1836
1836
|
.sp
|
1837
1837
|
After the above steps, \fB/reference/executables/groonga\fP is found in
|
1838
|
-
\fB/usr/local/bin/groonga\fP
|
1838
|
+
\fB/usr/local/bin/groonga\fP\&.
|
1839
1839
|
.sp
|
1840
1840
|
The default build will work well but you can customize groonga at
|
1841
1841
|
\fBconfigure\fP step.
|
@@ -1843,15 +1843,15 @@ The default build will work well but you can customize groonga at
|
|
1843
1843
|
The following describes details about each step.
|
1844
1844
|
.SS \fBconfigure\fP
|
1845
1845
|
.sp
|
1846
|
-
First, you need to run \fBconfigure\fP
|
1846
|
+
First, you need to run \fBconfigure\fP\&. Here are important \fBconfigure\fP
|
1847
1847
|
options:
|
1848
1848
|
.SS \fB\-\-prefix=PATH\fP
|
1849
1849
|
.sp
|
1850
1850
|
Specifies the install base directory. Groonga related files are
|
1851
1851
|
installed under \fB${PATH}/\fP directory.
|
1852
1852
|
.sp
|
1853
|
-
The default is \fB/usr/local\fP
|
1854
|
-
installed into \fB/usr/local/bin/groonga\fP
|
1853
|
+
The default is \fB/usr/local\fP\&. In this case, \fB/reference/executables/groonga\fP is
|
1854
|
+
installed into \fB/usr/local/bin/groonga\fP\&.
|
1855
1855
|
.sp
|
1856
1856
|
Here is an example that installs groonga into \fB~/local\fP for an user
|
1857
1857
|
use instead of system wide use:
|
@@ -1869,9 +1869,9 @@ use instead of system wide use:
|
|
1869
1869
|
.sp
|
1870
1870
|
Specifies the base directory to place modifiable file such as log
|
1871
1871
|
file, PID file and database files. For example, log file is placed at
|
1872
|
-
\fB${PATH}/log/groonga.log\fP
|
1872
|
+
\fB${PATH}/log/groonga.log\fP\&.
|
1873
1873
|
.sp
|
1874
|
-
The default is \fB/usr/local/var\fP
|
1874
|
+
The default is \fB/usr/local/var\fP\&.
|
1875
1875
|
.sp
|
1876
1876
|
Here is an example that system wide \fB/var\fP is used for modifiable
|
1877
1877
|
files:
|
@@ -1892,7 +1892,7 @@ path is \fB/reference/executables/groonga\fP command\(aqs \fB\-\-log\-path\fP
|
|
1892
1892
|
command line option. So this option is not critical build option. It\(aqs
|
1893
1893
|
just for convenient.
|
1894
1894
|
.sp
|
1895
|
-
The default is \fB/usr/local/var/log/groonga.log\fP
|
1895
|
+
The default is \fB/usr/local/var/log/groonga.log\fP\&. The
|
1896
1896
|
\fB/usr/local/var\fP part is changed by \fB\-\-localestatedir\fP option.
|
1897
1897
|
.sp
|
1898
1898
|
Here is an example that log file is placed into shared NFS directory
|
@@ -1910,9 +1910,9 @@ Here is an example that log file is placed into shared NFS directory
|
|
1910
1910
|
.SS \fB\-\-with\-default\-encoding=ENCODING\fP
|
1911
1911
|
.sp
|
1912
1912
|
Specifies the default encoding. Available encodings are \fBeuc_jp\fP,
|
1913
|
-
\fBsjis\fP, \fButf8\fP, \fBlatin1\fP, \fBkoi8r\fP and \fBnone\fP
|
1913
|
+
\fBsjis\fP, \fButf8\fP, \fBlatin1\fP, \fBkoi8r\fP and \fBnone\fP\&.
|
1914
1914
|
.sp
|
1915
|
-
The default is \fButf\-8\fP
|
1915
|
+
The default is \fButf\-8\fP\&.
|
1916
1916
|
.sp
|
1917
1917
|
Here is an example that Shift_JIS is used as the default encoding:
|
1918
1918
|
.INDENT 0.0
|
@@ -1966,7 +1966,7 @@ Here is an example that enables column value compression by zlib:
|
|
1966
1966
|
.INDENT 0.0
|
1967
1967
|
.INDENT 3.5
|
1968
1968
|
The disabled reason is that memory leak occurs when it refers column value.
|
1969
|
-
This is already known issue as \fI\%GitHub#6\fP
|
1969
|
+
This is already known issue as \fI\%GitHub#6\fP\&.
|
1970
1970
|
This issue is not nothing to do with updating column value.
|
1971
1971
|
.UNINDENT
|
1972
1972
|
.UNINDENT
|
@@ -1992,7 +1992,7 @@ Here is an example that enables column value compression by LZO:
|
|
1992
1992
|
.INDENT 0.0
|
1993
1993
|
.INDENT 3.5
|
1994
1994
|
The disabled reason is that memory leak occurs when it refers column value.
|
1995
|
-
This is already known issue as \fI\%GitHub#6\fP
|
1995
|
+
This is already known issue as \fI\%GitHub#6\fP\&.
|
1996
1996
|
This issue is not nothing to do with updating column value.
|
1997
1997
|
.UNINDENT
|
1998
1998
|
.UNINDENT
|
@@ -2004,9 +2004,9 @@ path that you use for building MessagePack.
|
|
2004
2004
|
.sp
|
2005
2005
|
If you installed MessagePack with \fB\-\-prefix=$HOME/local\fP option, you
|
2006
2006
|
sholud specify \fB\-\-with\-message\-pack=$HOME/local\fP to groonga\(aqs
|
2007
|
-
\fBconfigure\fP
|
2007
|
+
\fBconfigure\fP\&.
|
2008
2008
|
.sp
|
2009
|
-
The default is \fB/usr\fP
|
2009
|
+
The default is \fB/usr\fP\&.
|
2010
2010
|
.sp
|
2011
2011
|
Here is an example that uses MessagePack built with
|
2012
2012
|
\fB\-\-prefix=$HOME/local\fP option:
|
@@ -2023,7 +2023,7 @@ Here is an example that uses MessagePack built with
|
|
2023
2023
|
.SS \fB\-\-with\-munin\-plugins\fP
|
2024
2024
|
.sp
|
2025
2025
|
Installs Munin plugins for groonga. They are installed into
|
2026
|
-
\fB${PREFIX}/share/groonga/munin/plugins/\fP
|
2026
|
+
\fB${PREFIX}/share/groonga/munin/plugins/\fP\&.
|
2027
2027
|
.sp
|
2028
2028
|
Those plugins are not installed by default.
|
2029
2029
|
.sp
|
@@ -2041,7 +2041,7 @@ Here is an example that installs Munin plugins for groonga:
|
|
2041
2041
|
.SS \fB\-\-with\-package\-platform=PLATFORM\fP
|
2042
2042
|
.sp
|
2043
2043
|
Installs platform specific system management files such as init
|
2044
|
-
script. Available platforms are \fBredhat\fP and \fBfedora\fP
|
2044
|
+
script. Available platforms are \fBredhat\fP and \fBfedora\fP\&. \fBredhat\fP
|
2045
2045
|
is for Red Hat and Red Hat clone distributions such as
|
2046
2046
|
CentOS. \fBfedora\fP is for Fedora.
|
2047
2047
|
.sp
|
@@ -2106,7 +2106,7 @@ Now, you can install built groonga!:
|
|
2106
2106
|
.UNINDENT
|
2107
2107
|
.sp
|
2108
2108
|
If you have write permission for \fB${PREFIX}\fP, you don\(aqt need to use
|
2109
|
-
\fBsudo\fP
|
2109
|
+
\fBsudo\fP\&. e.g. \fB\-\-prefix=$HOME/local\fP case. In this case, use \fBmake
|
2110
2110
|
install\fP:
|
2111
2111
|
.INDENT 0.0
|
2112
2112
|
.INDENT 3.5
|
@@ -2259,7 +2259,7 @@ In the second form, you can specify a parameter name with its value. So, the ord
|
|
2259
2259
|
.sp
|
2260
2260
|
If you want to specify a value which contains white\-spaces or special characters, such as quotes and parentheses, please enclose the value with single\-quotes or double\-quotes.
|
2261
2261
|
.sp
|
2262
|
-
For details, see also the paragraph of "command" in \fB/reference/executables/groonga\fP
|
2262
|
+
For details, see also the paragraph of "command" in \fB/reference/executables/groonga\fP\&.
|
2263
2263
|
.SS Basic commands
|
2264
2264
|
.INDENT 0.0
|
2265
2265
|
.INDENT 3.5
|
@@ -3572,7 +3572,7 @@ select \-\-table Site \-\-query title:@this
|
|
3572
3572
|
.UNINDENT
|
3573
3573
|
.SS Administration tool (HTTP)
|
3574
3574
|
.sp
|
3575
|
-
An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing \fI\%http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/\fP
|
3575
|
+
An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing \fI\%http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/\fP\&. Note that Javascript must be enabled for the tool to work properly.
|
3576
3576
|
.SS Security issues
|
3577
3577
|
.sp
|
3578
3578
|
Groonga servers don\(aqt support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.
|
@@ -3581,7 +3581,7 @@ Groonga servers don\(aqt support user authentication. Everyone can view and modi
|
|
3581
3581
|
Groonga is a full text search engine but also serves as a column\-oriented data store. Groonga supports various data types, such as numeric types, string types, date and time type, longitude and latitude types, etc. This tutorial shows a list of data types and explains how to use them.
|
3582
3582
|
.SS Overview
|
3583
3583
|
.sp
|
3584
|
-
The basic data types of Groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP
|
3584
|
+
The basic data types of Groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP\&.
|
3585
3585
|
.sp
|
3586
3586
|
In addition, Groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.
|
3587
3587
|
.sp
|
@@ -3663,7 +3663,7 @@ select \-\-table ToyBox \-\-output_columns _key,is_animal
|
|
3663
3663
|
.UNINDENT
|
3664
3664
|
.SS Numeric types
|
3665
3665
|
.sp
|
3666
|
-
The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/types\fP
|
3666
|
+
The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/types\fP\&. The default value of the numeric types is 0.
|
3667
3667
|
.sp
|
3668
3668
|
The following example creates an Int8 column and a Float column, and then updates existing records. The \fB/reference/commands/load\fP command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes \-56. Note that the result of an overflow/underflow is undefined.
|
3669
3669
|
.sp
|
@@ -3734,7 +3734,7 @@ select \-\-table ToyBox \-\-output_columns _key,price,weight
|
|
3734
3734
|
.UNINDENT
|
3735
3735
|
.SS String types
|
3736
3736
|
.sp
|
3737
|
-
The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP
|
3737
|
+
The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP\&. The default value is the zero\-length string.
|
3738
3738
|
.sp
|
3739
3739
|
The following example creates a ShortText column and updates existing records. The third record has the default value because not updated.
|
3740
3740
|
.sp
|
@@ -3864,7 +3864,7 @@ select \-\-table ToyBox \-\-output_columns _key,time
|
|
3864
3864
|
.UNINDENT
|
3865
3865
|
.SS Longitude and latitude types
|
3866
3866
|
.sp
|
3867
|
-
The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP
|
3867
|
+
The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP\&. To represent a longitude and latitude, Groonga uses a string formatted as follows:
|
3868
3868
|
.INDENT 0.0
|
3869
3869
|
.IP \(bu 2
|
3870
3870
|
"longitude x latitude" in milliseconds (e.g.: "128452975x503157902")
|
@@ -4641,7 +4641,7 @@ As you know, there is a naive solution to execute query by every the value of co
|
|
4641
4641
|
.sp
|
4642
4642
|
If you are familiar with SQL, you will doubt with "Is there a similar SQL functionality to \fBGROUP BY\fP in Groonga?".
|
4643
4643
|
.sp
|
4644
|
-
Of course, Groonga provides such a functionality. It\(aqs called as \fBdrilldown\fP
|
4644
|
+
Of course, Groonga provides such a functionality. It\(aqs called as \fBdrilldown\fP\&.
|
4645
4645
|
.sp
|
4646
4646
|
\fBdrilldown\fP enables you to get the number of records which belongs to specific the value of column at once.
|
4647
4647
|
.sp
|
@@ -4787,7 +4787,7 @@ Group records means following records
|
|
4787
4787
|
T}
|
4788
4788
|
_
|
4789
4789
|
T{
|
4790
|
-
|
4790
|
+
\&.org
|
4791
4791
|
T} T{
|
4792
4792
|
3
|
4793
4793
|
T} T{
|
@@ -4802,7 +4802,7 @@ T} T{
|
|
4802
4802
|
T}
|
4803
4803
|
_
|
4804
4804
|
T{
|
4805
|
-
|
4805
|
+
\&.net
|
4806
4806
|
T} T{
|
4807
4807
|
3
|
4808
4808
|
T} T{
|
@@ -4817,7 +4817,7 @@ T} T{
|
|
4817
4817
|
T}
|
4818
4818
|
_
|
4819
4819
|
T{
|
4820
|
-
|
4820
|
+
\&.com
|
4821
4821
|
T} T{
|
4822
4822
|
3
|
4823
4823
|
T} T{
|
@@ -7951,7 +7951,7 @@ select Doc \-\-match_columns body \-\-query "シークヮーサー" \-\-query_ex
|
|
7951
7951
|
Groonga has the suggest feature. This section describes how to use it and how it works.
|
7952
7952
|
.SS Introduction
|
7953
7953
|
.sp
|
7954
|
-
The suggest feature in
|
7954
|
+
The suggest feature in Groonga provides the following features:
|
7955
7955
|
.INDENT 0.0
|
7956
7956
|
.IP \(bu 2
|
7957
7957
|
Completion
|
@@ -7963,7 +7963,7 @@ Suggestion
|
|
7963
7963
|
.SS Completion
|
7964
7964
|
.sp
|
7965
7965
|
Completion helps user input. If user inputs a partial word,
|
7966
|
-
|
7966
|
+
Groonga can return complete words from registered
|
7967
7967
|
words.
|
7968
7968
|
.sp
|
7969
7969
|
For example, there are registered words:
|
@@ -9165,7 +9165,7 @@ If you use \fBgroonga\-httpd\fP package, you can also take benefits of nginx fun
|
|
9165
9165
|
.sp
|
9166
9166
|
We recommend to use \fBgroonga\-server\-http\fP at first, then if you want to use more
|
9167
9167
|
fullfilling functionality, use \fBgroonga\-httpd\fP package. If you have performance issues which
|
9168
|
-
is derived from protocol overheads, consider to use \fBgroonga\-server\-gqtp\fP
|
9168
|
+
is derived from protocol overheads, consider to use \fBgroonga\-server\-gqtp\fP\&.
|
9169
9169
|
.INDENT 0.0
|
9170
9170
|
.INDENT 3.5
|
9171
9171
|
.sp
|
@@ -9580,7 +9580,7 @@ Restarting groonga HTTP server(Fedora):
|
|
9580
9580
|
.sp
|
9581
9581
|
TODO
|
9582
9582
|
.sp
|
9583
|
-
See \fB/reference/executables/groonga\fP
|
9583
|
+
See \fB/reference/executables/groonga\fP\&.
|
9584
9584
|
.SS HTTP
|
9585
9585
|
.sp
|
9586
9586
|
Groonga provides two HTTP server implementations.
|
@@ -9607,7 +9607,7 @@ implementation. It is also fast and has many HTTP features.
|
|
9607
9607
|
.SS Comparison
|
9608
9608
|
.sp
|
9609
9609
|
There are many differences between \fBgroonga\fP and
|
9610
|
-
\fBgroonga\-httpd\fP
|
9610
|
+
\fBgroonga\-httpd\fP\&. Here is a comparison table.
|
9611
9611
|
.TS
|
9612
9612
|
center;
|
9613
9613
|
|l|l|l|.
|
@@ -9795,8 +9795,8 @@ http {
|
|
9795
9795
|
.SS Custom prefix path
|
9796
9796
|
.sp
|
9797
9797
|
\fBgroonga\fP accepts a path that starts with \fB/d/\fP as command URL
|
9798
|
-
such as \fBhttp://localhost:10041/d/status\fP
|
9799
|
-
prefix path \fB/d/\fP
|
9798
|
+
such as \fBhttp://localhost:10041/d/status\fP\&. You cannot change the
|
9799
|
+
prefix path \fB/d/\fP\&.
|
9800
9800
|
.sp
|
9801
9801
|
\fBgroonga\-httpd\fP can custom prefix path. For example, you can use
|
9802
9802
|
\fBhttp://localhost:10041/api/status\fP as command URL. Here is a sample
|
@@ -9915,7 +9915,7 @@ http {
|
|
9915
9915
|
.sp
|
9916
9916
|
HTTP supports authentications such as basic authentication and digest
|
9917
9917
|
authentication. It can be used for restricting use of danger command such
|
9918
|
-
as \fB/reference/commands/shutdown\fP
|
9918
|
+
as \fB/reference/commands/shutdown\fP\&.
|
9919
9919
|
.sp
|
9920
9920
|
\fBgroonga\fP doesn\(aqt support any authentications. To restrict use of
|
9921
9921
|
danger command, other tools such as iptables and reverse proxy are
|
@@ -9994,7 +9994,7 @@ Note that \fIgzip_types *\fP is specified. It\(aqs one of the important
|
|
9994
9994
|
configuration. \fIgzip_types\fP specifies gzip target data formats by MIME
|
9995
9995
|
types. \fBgroonga\-httpd\fP returns one of JSON, XML or MessagePack
|
9996
9996
|
format data. But those formats aren\(aqt included in the default value of
|
9997
|
-
\fIgzip_types\fP
|
9997
|
+
\fIgzip_types\fP\&. The default value of \fIgzip_types\fP is \fItext/html\fP\&.
|
9998
9998
|
.sp
|
9999
9999
|
To compress response data from \fBgroonga\-httpd\fP by gzip, you need
|
10000
10000
|
to specify \fIgzip_types *\fP or \fIgzip_types application/json text/xml
|
@@ -10008,11 +10008,11 @@ You can load your data by POST JSON data. You need follow the
|
|
10008
10008
|
following rules to use loading by POST.
|
10009
10009
|
.INDENT 0.0
|
10010
10010
|
.IP \(bu 2
|
10011
|
-
\fIContent\-Type\fP header value must be \fIapplication/json\fP
|
10011
|
+
\fIContent\-Type\fP header value must be \fIapplication/json\fP\&.
|
10012
10012
|
.IP \(bu 2
|
10013
10013
|
JSON data is sent as body.
|
10014
10014
|
.IP \(bu 2
|
10015
|
-
Table name is specified by query parameter such as \fBtable=NAME\fP
|
10015
|
+
Table name is specified by query parameter such as \fBtable=NAME\fP\&.
|
10016
10016
|
.UNINDENT
|
10017
10017
|
.sp
|
10018
10018
|
Here is an example curl command line that loads two users \fIalice\fP and
|
@@ -10065,7 +10065,7 @@ grnslap [options] [dest]
|
|
10065
10065
|
.sp
|
10066
10066
|
grnslapは、groongaプロセスに対してリクエストを多重に行い、パフォーマンスをチェックするためのツールです。
|
10067
10067
|
.sp
|
10068
|
-
|
10068
|
+
Groonga独自プロトコルであるGQTPと、httpの両プロトコルでリクエストを行うことができます。また、リクエストの多重度を指定することができます。
|
10069
10069
|
.sp
|
10070
10070
|
クエリの内容を標準入力から与えることができます。実稼動環境でのクエリパタンに近いクエリを標準入力に与えることによって、実稼動環境に近い状態での検証を行うことができます。
|
10071
10071
|
.sp
|
@@ -10133,8 +10133,8 @@ groonga [options] [dest] [command [args]]
|
|
10133
10133
|
.UNINDENT
|
10134
10134
|
.SS 説明
|
10135
10135
|
.sp
|
10136
|
-
|
10137
|
-
|
10136
|
+
Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンです。
|
10137
|
+
Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通して操作することができます。このマニュアルページでは、groongaコマンドの使い方について説明します。
|
10138
10138
|
.SS オプション
|
10139
10139
|
.INDENT 0.0
|
10140
10140
|
.TP
|
@@ -10777,13 +10777,13 @@ groonga サーバが動作していないか? groonga\-benchmarkは、\-i, \
|
|
10777
10777
|
.sp
|
10778
10778
|
groonga\-httpd is a program to communicate with a groonga server using
|
10779
10779
|
the HTTP protocol. It functions as same as
|
10780
|
-
\fBgroonga\-server\-http\fP
|
10780
|
+
\fBgroonga\-server\-http\fP\&. Although \fBgroonga\-server\-http\fP has
|
10781
10781
|
limited support for HTTP with a minimal built\-in HTTP server,
|
10782
|
-
groonga\-httpd has full support for HTTP with an embedded \fI\%nginx\fP
|
10782
|
+
groonga\-httpd has full support for HTTP with an embedded \fI\%nginx\fP\&. All standards\-compliance and features provided
|
10783
10783
|
by nginx is also available in groonga\-httpd.
|
10784
10784
|
.sp
|
10785
10785
|
groonga\-httpd has an Web\-based administration tool implemented with HTML and
|
10786
|
-
JavaScript. You can access to it from \fI\%http://hostname:port/\fP
|
10786
|
+
JavaScript. You can access to it from \fI\%http://hostname:port/\fP\&.
|
10787
10787
|
.SS Synopsis
|
10788
10788
|
.INDENT 0.0
|
10789
10789
|
.INDENT 3.5
|
@@ -10873,7 +10873,7 @@ Execution example:
|
|
10873
10873
|
.UNINDENT
|
10874
10874
|
.SS Browse the administration tool
|
10875
10875
|
.sp
|
10876
|
-
Also, you can browse Web\-based administration tool at \fI\%http://localhost:10041/\fP
|
10876
|
+
Also, you can browse Web\-based administration tool at \fI\%http://localhost:10041/\fP\&.
|
10877
10877
|
.SS Shut down
|
10878
10878
|
.sp
|
10879
10879
|
Finally, to terminate the running groonga\-httpd daemon, run this:
|
@@ -10921,7 +10921,7 @@ groonga on | off;
|
|
10921
10921
|
.UNINDENT
|
10922
10922
|
.sp
|
10923
10923
|
Specifies whether groonga is enabled in the \fBlocation\fP block. The
|
10924
|
-
default is \fBoff\fP
|
10924
|
+
default is \fBoff\fP\&. You need to specify \fBon\fP to enable groonga.
|
10925
10925
|
.sp
|
10926
10926
|
Examples:
|
10927
10927
|
.INDENT 0.0
|
@@ -10995,7 +10995,7 @@ nothing.
|
|
10995
10995
|
If parent directory doesn\(aqt exist, parent directory is also created
|
10996
10996
|
recursively.
|
10997
10997
|
.sp
|
10998
|
-
The default value is \fBon\fP
|
10998
|
+
The default value is \fBon\fP\&. Normally, the value doesn\(aqt need to be
|
10999
10999
|
changed.
|
11000
11000
|
.SS \fBgroonga_base_path\fP
|
11001
11001
|
.sp
|
@@ -11020,7 +11020,7 @@ The same value as \fBlocation\fP name.
|
|
11020
11020
|
.UNINDENT
|
11021
11021
|
.sp
|
11022
11022
|
Specifies the base path in URI. groonga uses
|
11023
|
-
\fB/d/command?parameter1=value1&...\fP path to run \fBcommand\fP
|
11023
|
+
\fB/d/command?parameter1=value1&...\fP path to run \fBcommand\fP\&. The form
|
11024
11024
|
of path in used in groonga\-httpd but groonga\-httpd also supports
|
11025
11025
|
\fB/other\-prefix/command?parameter1=value1&...\fP form. To support the
|
11026
11026
|
form, groonga\-httpd removes the base path from the head of request URI
|
@@ -11083,8 +11083,8 @@ groonga_log_path path | off;
|
|
11083
11083
|
.UNINDENT
|
11084
11084
|
.sp
|
11085
11085
|
Specifies groonga log path in the \fBhttp\fP, \fBserver\fP or \fBlocation\fP block. The
|
11086
|
-
default is \fB/var/log/groonga/httpd/groonga.log\fP
|
11087
|
-
You can disable logging to specify \fBoff\fP
|
11086
|
+
default is \fB/var/log/groonga/httpd/groonga.log\fP\&.
|
11087
|
+
You can disable logging to specify \fBoff\fP\&.
|
11088
11088
|
.sp
|
11089
11089
|
Examples:
|
11090
11090
|
.INDENT 0.0
|
@@ -11124,7 +11124,7 @@ groonga_log_level none | emergency | alert | ciritical | error | warning | notic
|
|
11124
11124
|
.UNINDENT
|
11125
11125
|
.sp
|
11126
11126
|
Specifies groonga log level in the \fBhttp\fP, \fBserver\fP or \fBlocation\fP block. The
|
11127
|
-
default is \fBnotice\fP
|
11127
|
+
default is \fBnotice\fP\&. You can disable logging by specifying \fBnone\fP as log level.
|
11128
11128
|
.sp
|
11129
11129
|
Examples:
|
11130
11130
|
.INDENT 0.0
|
@@ -11165,8 +11165,8 @@ groonga_query_log_path path | off;
|
|
11165
11165
|
.sp
|
11166
11166
|
Specifies groonga\(aqs query log path in the \fBhttp\fP, \fBserver\fP or
|
11167
11167
|
\fBlocation\fP block. The default is
|
11168
|
-
\fB/var/log/groonga/httpd/groonga\-query.log\fP
|
11169
|
-
to specify \fBoff\fP
|
11168
|
+
\fB/var/log/groonga/httpd/groonga\-query.log\fP\&. You can disable logging
|
11169
|
+
to specify \fBoff\fP\&.
|
11170
11170
|
.sp
|
11171
11171
|
Examples:
|
11172
11172
|
.INDENT 0.0
|
@@ -11196,7 +11196,7 @@ Debugging.
|
|
11196
11196
|
.UNINDENT
|
11197
11197
|
.UNINDENT
|
11198
11198
|
.sp
|
11199
|
-
You can analyze your query log by \fI\%groonga\-query\-log package\fP
|
11199
|
+
You can analyze your query log by \fI\%groonga\-query\-log package\fP\&. The package provides
|
11200
11200
|
useful tools.
|
11201
11201
|
.sp
|
11202
11202
|
For example, there is a tool that analyzing your query log. It can
|
@@ -11213,7 +11213,7 @@ many cases, groonga queries may be CPU\-intensive work, so to fully utilize
|
|
11213
11213
|
multi\-CPU/core systems, it\(aqs essential to set this accordingly.
|
11214
11214
|
.sp
|
11215
11215
|
This isn\(aqt a groonga\-httpd specific directive, but an nginx\(aqs one. For details,
|
11216
|
-
see \fI\%http://wiki.nginx.org/CoreModule#worker_processes\fP
|
11216
|
+
see \fI\%http://wiki.nginx.org/CoreModule#worker_processes\fP\&.
|
11217
11217
|
.sp
|
11218
11218
|
By default, this is set to 1. It is nginx\(aqs default.
|
11219
11219
|
.SS \fBgroonga_cache_limit\fP
|
@@ -11432,7 +11432,7 @@ cache by hand. It is done automatically.
|
|
11432
11432
|
All standard HTTP modules are available. HttpRewriteModule is
|
11433
11433
|
disabled when you don\(aqt have PCRE (Perl Compatible Regular
|
11434
11434
|
Expressions). For the list of standard HTTP modules, see
|
11435
|
-
\fI\%http://wiki.nginx.org/Modules\fP
|
11435
|
+
\fI\%http://wiki.nginx.org/Modules\fP\&.
|
11436
11436
|
.SS groonga HTTPサーバー
|
11437
11437
|
.SS 名前
|
11438
11438
|
.sp
|
@@ -11509,9 +11509,9 @@ groonga\-suggest\-create\-dataset [options] DATABASE DATASET
|
|
11509
11509
|
.UNINDENT
|
11510
11510
|
.SS DESCTIPION
|
11511
11511
|
.sp
|
11512
|
-
groonga\-suggest\-create\-dataset creates a dataset for \fB/suggest\fP
|
11512
|
+
groonga\-suggest\-create\-dataset creates a dataset for \fB/suggest\fP\&. A database has many datasets. This command just defines schema for a suggestion dataset.
|
11513
11513
|
.sp
|
11514
|
-
This command generates some tables and columns for \fB/suggest\fP
|
11514
|
+
This command generates some tables and columns for \fB/suggest\fP\&.
|
11515
11515
|
.sp
|
11516
11516
|
Here is the list of such tables. If you specify \(aqquery\(aq as dataset name, following \(aq_DATASET\(aq suffix are replaced. Thus, \(aqitem_query\(aq, \(aqpair_query\(aq, \(aqsequence_query\(aq, \(aqevent_query\(aq tables are generated.
|
11517
11517
|
.INDENT 0.0
|
@@ -11610,7 +11610,7 @@ Specify this option to disable checking max fd on start.
|
|
11610
11610
|
.UNINDENT
|
11611
11611
|
.SS Parameters
|
11612
11612
|
.sp
|
11613
|
-
There is one required parameter \- \fBdatabase_path\fP
|
11613
|
+
There is one required parameter \- \fBdatabase_path\fP\&.
|
11614
11614
|
.SS \fBdatabase_path\fP
|
11615
11615
|
.sp
|
11616
11616
|
Specifies the path to a groonga database.
|
@@ -11637,7 +11637,7 @@ TODO
|
|
11637
11637
|
TODO
|
11638
11638
|
.SS Parameters
|
11639
11639
|
.sp
|
11640
|
-
There is one required parameter \- \fBdatabase_path\fP
|
11640
|
+
There is one required parameter \- \fBdatabase_path\fP\&.
|
11641
11641
|
.SS \fBdatabase_path\fP
|
11642
11642
|
.sp
|
11643
11643
|
Specifies the path to a groonga database.
|
@@ -11678,7 +11678,7 @@ They provides different ways to change output format type.
|
|
11678
11678
|
.SS Command line
|
11679
11679
|
.sp
|
11680
11680
|
You can use command line query interface by \fBgroonga
|
11681
|
-
DB_PATH\fP or \fBgroonga \-c\fP
|
11681
|
+
DB_PATH\fP or \fBgroonga \-c\fP\&. Those groonga commands shows
|
11682
11682
|
\fB> \(ga\(ga prompt. In this query interface, you can specify
|
11683
11683
|
output format type by \(ga\(gaoutput_type\fP option.
|
11684
11684
|
.sp
|
@@ -11785,7 +11785,7 @@ get a result in MessagePack format:
|
|
11785
11785
|
.SS HTTP
|
11786
11786
|
.sp
|
11787
11787
|
You can use HTTP query interface by \fBgroonga \-\-protocol
|
11788
|
-
http \-s DB_PATH\fP
|
11788
|
+
http \-s DB_PATH\fP\&. Groonga HTTP server starts on port 10041
|
11789
11789
|
by default. In this query interface, you can specify
|
11790
11790
|
output format type by extension.
|
11791
11791
|
.sp
|
@@ -12133,7 +12133,7 @@ The following part is \fBBODY\fP:
|
|
12133
12133
|
.UNINDENT
|
12134
12134
|
.UNINDENT
|
12135
12135
|
.sp
|
12136
|
-
The first element is always \fB0\fP
|
12136
|
+
The first element is always \fB0\fP\&.
|
12137
12137
|
.sp
|
12138
12138
|
\fBUNIX_TIME_WHEN_COMMAND_IS_STARTED\fP is the number of seconds
|
12139
12139
|
since 1970\-01\-01 00:00:00 UTC when the command is started
|
@@ -12242,7 +12242,7 @@ array. \fBLOCATION_IN_GROONGA\fP has three elements:
|
|
12242
12242
|
is occurred.
|
12243
12243
|
.sp
|
12244
12244
|
\fBLINE_CONTENT\fP is the content at \fBLINE_NUMBER\fP in
|
12245
|
-
\fBINPUT_FILE_NAME\fP
|
12245
|
+
\fBINPUT_FILE_NAME\fP\&.
|
12246
12246
|
.SS \fBBODY\fP
|
12247
12247
|
.sp
|
12248
12248
|
\fBBODY\fP content depends on the executed command. It may be omitted.
|
@@ -12525,7 +12525,7 @@ max number of query cache entries.
|
|
12525
12525
|
\fBHEADER\fP
|
12526
12526
|
.INDENT 0.0
|
12527
12527
|
.INDENT 3.5
|
12528
|
-
See \fB/reference/command/output_format\fP about \fBHEADER\fP
|
12528
|
+
See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
|
12529
12529
|
.UNINDENT
|
12530
12530
|
.UNINDENT
|
12531
12531
|
.sp
|
@@ -12941,10 +12941,10 @@ There are two flags to compress the value of column, but you can\(aqt specify th
|
|
12941
12941
|
.INDENT 0.0
|
12942
12942
|
.TP
|
12943
12943
|
.B 16, \fBCOMPRESS_ZLIB\fP
|
12944
|
-
Reserved. Compress the value of column by using zlib. This flag is disabled feature even if you build groonga with \fB\-\-with\-zlib\fP
|
12944
|
+
Reserved. Compress the value of column by using zlib. This flag is disabled feature even if you build groonga with \fB\-\-with\-zlib\fP\&.
|
12945
12945
|
.TP
|
12946
12946
|
.B 32, \fBCOMPRESS_LZO\fP
|
12947
|
-
Reserved. Compress the value of column by using lzo. This flag is disabled feature even if you build groonga with \fB\-\-with\-lzo\fP
|
12947
|
+
Reserved. Compress the value of column by using lzo. This flag is disabled feature even if you build groonga with \fB\-\-with\-lzo\fP\&.
|
12948
12948
|
.UNINDENT
|
12949
12949
|
.sp
|
12950
12950
|
インデックス型のカラムについては、flagsの値に以下の値を加えることによって、追加の属
|
@@ -13372,10 +13372,10 @@ select Users
|
|
13372
13372
|
.UNINDENT
|
13373
13373
|
.SS Parameters
|
13374
13374
|
.sp
|
13375
|
-
This section describes parameters of \fBcolumn_rename\fP
|
13375
|
+
This section describes parameters of \fBcolumn_rename\fP\&.
|
13376
13376
|
.SS Required parameter
|
13377
13377
|
.sp
|
13378
|
-
There are required parameters, \fBtable_name\fP and \fBcolumn_name\fP
|
13378
|
+
There are required parameters, \fBtable_name\fP and \fBcolumn_name\fP\&.
|
13379
13379
|
.SS \fBtable_name\fP
|
13380
13380
|
.sp
|
13381
13381
|
It specifies the name of table.
|
@@ -14044,7 +14044,7 @@ If you specify "json" as \fBinput_type\fP, you can choose a format from below:
|
|
14044
14044
|
.sp
|
14045
14045
|
\fB[COLUMN_NAME1, COLUMN_NAME2,..]\fP format in \fBFormat 1\fP is effective only when \fBcolumn\fP parameter isn\(aqt specified.
|
14046
14046
|
.sp
|
14047
|
-
When a target table contains primary key, you must specify \fB_key\fP column (pseudo column associated primary key) as the one of \fBCOLUMN_NAME\fP
|
14047
|
+
When a target table contains primary key, you must specify \fB_key\fP column (pseudo column associated primary key) as the one of \fBCOLUMN_NAME\fP\&.
|
14048
14048
|
.sp
|
14049
14049
|
If \fBvalues\fP isn\(aqt specified any values, they are read from the standard input until all opened parenthes match their closed ones.
|
14050
14050
|
You don\(aqt have to enclose them with single\-quotes or double\-quotes, but if you specified values with \fBvalues\fP parameter, you should do.
|
@@ -14081,7 +14081,7 @@ column) columns is updated.
|
|
14081
14081
|
\fBinput_type\fP
|
14082
14082
|
.INDENT 0.0
|
14083
14083
|
.INDENT 3.5
|
14084
|
-
It specifies an input format for \fBvalues\fP
|
14084
|
+
It specifies an input format for \fBvalues\fP\&. It supports JSON only.
|
14085
14085
|
.UNINDENT
|
14086
14086
|
.UNINDENT
|
14087
14087
|
.SS Usage
|
@@ -14383,7 +14383,7 @@ It is useful for you to check the results of normalizer.
|
|
14383
14383
|
.SS Syntax
|
14384
14384
|
.sp
|
14385
14385
|
\fBnormalize\fP commands has two required parameters. They are
|
14386
|
-
\fBnormalizer\fP and \fBstring\fP
|
14386
|
+
\fBnormalizer\fP and \fBstring\fP\&.
|
14387
14387
|
.INDENT 0.0
|
14388
14388
|
.INDENT 3.5
|
14389
14389
|
.sp
|
@@ -14424,14 +14424,14 @@ normalize NormalizerAuto "aBcDe 123"
|
|
14424
14424
|
.UNINDENT
|
14425
14425
|
.SS Parameters
|
14426
14426
|
.sp
|
14427
|
-
This section describes parameters of \fBnormalizer\fP
|
14427
|
+
This section describes parameters of \fBnormalizer\fP\&.
|
14428
14428
|
.SS Required parameter
|
14429
14429
|
.sp
|
14430
|
-
There are required parameters, \fBnormalizer\fP and \fBstring\fP
|
14430
|
+
There are required parameters, \fBnormalizer\fP and \fBstring\fP\&.
|
14431
14431
|
.SS \fBnormalizer\fP
|
14432
14432
|
.sp
|
14433
14433
|
It specifies the normalizer name. \fBnormalize\fP command uses the
|
14434
|
-
normalizer that is named \fBnormalizer\fP
|
14434
|
+
normalizer that is named \fBnormalizer\fP\&.
|
14435
14435
|
.sp
|
14436
14436
|
See \fB/reference/normalizers\fP about built\-in normalizers.
|
14437
14437
|
.sp
|
@@ -14441,7 +14441,7 @@ TODO
|
|
14441
14441
|
.sp
|
14442
14442
|
If you want to use other normalizers, you need to register additional
|
14443
14443
|
normalizer plugin by \fBregister\fP command. For example, you can use
|
14444
|
-
MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP
|
14444
|
+
MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP\&.
|
14445
14445
|
.SS \fBstring\fP
|
14446
14446
|
.sp
|
14447
14447
|
It specifies any string which you want to normalize.
|
@@ -14449,7 +14449,7 @@ It specifies any string which you want to normalize.
|
|
14449
14449
|
If you want to include spaces in \fBstring\fP, you need to quote
|
14450
14450
|
\fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
|
14451
14451
|
.sp
|
14452
|
-
Here is an example to use spaces in \fBstring\fP
|
14452
|
+
Here is an example to use spaces in \fBstring\fP\&.
|
14453
14453
|
.sp
|
14454
14454
|
TODO
|
14455
14455
|
.SS Optional parameters
|
@@ -14459,7 +14459,7 @@ There are optional parameters.
|
|
14459
14459
|
.sp
|
14460
14460
|
It specifies a normalization customize options. You can specify
|
14461
14461
|
multiple options separated by "\fB|\fP". For example,
|
14462
|
-
\fBREMOVE_BLANK|WITH_TYPES\fP
|
14462
|
+
\fBREMOVE_BLANK|WITH_TYPES\fP\&.
|
14463
14463
|
.sp
|
14464
14464
|
Here are available flags.
|
14465
14465
|
.TS
|
@@ -14504,15 +14504,15 @@ T}
|
|
14504
14504
|
_
|
14505
14505
|
.TE
|
14506
14506
|
.sp
|
14507
|
-
Here is an example that uses \fBREMOVE_BLANK\fP
|
14507
|
+
Here is an example that uses \fBREMOVE_BLANK\fP\&.
|
14508
14508
|
.sp
|
14509
14509
|
TODO
|
14510
14510
|
.sp
|
14511
|
-
Here is an example that uses \fBWITH_TYPES\fP
|
14511
|
+
Here is an example that uses \fBWITH_TYPES\fP\&.
|
14512
14512
|
.sp
|
14513
14513
|
TODO
|
14514
14514
|
.sp
|
14515
|
-
Here is an example that uses \fBREMOVE_TOKENIZED_DELIMITER\fP
|
14515
|
+
Here is an example that uses \fBREMOVE_TOKENIZED_DELIMITER\fP\&.
|
14516
14516
|
.sp
|
14517
14517
|
TODO
|
14518
14518
|
.SS Return value
|
@@ -14559,7 +14559,7 @@ T{
|
|
14559
14559
|
\fBtypes\fP
|
14560
14560
|
T} T{
|
14561
14561
|
An array of types of the normalized text. The N\-th \fBtypes\fP shows
|
14562
|
-
the type of the N\-th character in \fBnormalized\fP
|
14562
|
+
the type of the N\-th character in \fBnormalized\fP\&.
|
14563
14563
|
T}
|
14564
14564
|
_
|
14565
14565
|
.TE
|
@@ -14626,7 +14626,7 @@ Registered plugins can\(aqt be removed for now.
|
|
14626
14626
|
.UNINDENT
|
14627
14627
|
.SS Syntax
|
14628
14628
|
.sp
|
14629
|
-
\fBregister\fP has a parameter \fBpath\fP
|
14629
|
+
\fBregister\fP has a parameter \fBpath\fP\&. It is required parameter:
|
14630
14630
|
.INDENT 0.0
|
14631
14631
|
.INDENT 3.5
|
14632
14632
|
.sp
|
@@ -14641,7 +14641,7 @@ register path
|
|
14641
14641
|
.sp
|
14642
14642
|
Here is a sample that registers \fBQueryExpanderTSV\fP query expander
|
14643
14643
|
that is included in
|
14644
|
-
\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP
|
14644
|
+
\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
|
14645
14645
|
.sp
|
14646
14646
|
Execution example:
|
14647
14647
|
.INDENT 0.0
|
@@ -14656,11 +14656,11 @@ register query_expanders/tsv
|
|
14656
14656
|
.UNINDENT
|
14657
14657
|
.UNINDENT
|
14658
14658
|
.sp
|
14659
|
-
You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB
|
14659
|
+
You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
|
14660
14660
|
They are completed automatically.
|
14661
14661
|
.sp
|
14662
14662
|
You can specify absolute path such as \fBregister
|
14663
|
-
/usr/lib/groonga/plugins/query_expanders/tsv.so\fP
|
14663
|
+
/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
|
14664
14664
|
.SS Return value
|
14665
14665
|
.sp
|
14666
14666
|
\fBregister\fP returns \fBtrue\fP as body on success such as:
|
@@ -14675,9 +14675,9 @@ You can specify absolute path such as \fBregister
|
|
14675
14675
|
.UNINDENT
|
14676
14676
|
.UNINDENT
|
14677
14677
|
.sp
|
14678
|
-
If \fBregister\fP fails, error details are in \fBHEADER\fP
|
14678
|
+
If \fBregister\fP fails, error details are in \fBHEADER\fP\&.
|
14679
14679
|
.sp
|
14680
|
-
See \fB/reference/command/output_format\fP for \fBHEADER\fP
|
14680
|
+
See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
|
14681
14681
|
.SS \fBruby_eval\fP
|
14682
14682
|
.SS Summary
|
14683
14683
|
.sp
|
@@ -14697,7 +14697,7 @@ ruby_eval script
|
|
14697
14697
|
.UNINDENT
|
14698
14698
|
.SS Usage
|
14699
14699
|
.sp
|
14700
|
-
You can execute any scripts which mruby supports by calling \fBruby_eval\fP
|
14700
|
+
You can execute any scripts which mruby supports by calling \fBruby_eval\fP\&.
|
14701
14701
|
.sp
|
14702
14702
|
Here is an example that just calculate \fB1 + 2\fP as Ruby script.
|
14703
14703
|
.sp
|
@@ -14744,14 +14744,14 @@ exception information (Including metadata isn\(aqt implemented yet):
|
|
14744
14744
|
\fBHEADER\fP
|
14745
14745
|
.INDENT 0.0
|
14746
14746
|
.INDENT 3.5
|
14747
|
-
See \fB/reference/command/output_format\fP about \fBHEADER\fP
|
14747
|
+
See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
|
14748
14748
|
.UNINDENT
|
14749
14749
|
.UNINDENT
|
14750
14750
|
.sp
|
14751
14751
|
\fBEVALUATED_VALUE\fP
|
14752
14752
|
.INDENT 0.0
|
14753
14753
|
.INDENT 3.5
|
14754
|
-
\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP
|
14754
|
+
\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP\&.
|
14755
14755
|
.sp
|
14756
14756
|
\fBruby_eval\fP supports only a number for evaluated value for now.
|
14757
14757
|
Supported types will be increased in the future.
|
@@ -14777,7 +14777,7 @@ ruby_load path
|
|
14777
14777
|
.UNINDENT
|
14778
14778
|
.SS Usage
|
14779
14779
|
.sp
|
14780
|
-
You can load any script file which mruby supports by calling \fBruby_load\fP
|
14780
|
+
You can load any script file which mruby supports by calling \fBruby_load\fP\&.
|
14781
14781
|
.sp
|
14782
14782
|
Here is an example that just load \fBexpression.rb\fP as Ruby script.
|
14783
14783
|
.sp
|
@@ -14824,7 +14824,7 @@ exception information (Including metadata isn\(aqt implemented yet):
|
|
14824
14824
|
\fBHEADER\fP
|
14825
14825
|
.INDENT 0.0
|
14826
14826
|
.INDENT 3.5
|
14827
|
-
See \fB/reference/command/output_format\fP about \fBHEADER\fP
|
14827
|
+
See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
|
14828
14828
|
.UNINDENT
|
14829
14829
|
.UNINDENT
|
14830
14830
|
.sp
|
@@ -14930,7 +14930,7 @@ load \-\-table Entries
|
|
14930
14930
|
.sp
|
14931
14931
|
There is a table, \fBEntries\fP, for blog entries. An entry has title,
|
14932
14932
|
content and the number of likes for the entry. Title is key of
|
14933
|
-
\fBEntries\fP
|
14933
|
+
\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
|
14934
14934
|
number of likes is value of \fBEntries.n_likes\fP column.
|
14935
14935
|
.sp
|
14936
14936
|
\fBEntries._key\fP column and \fBEntries.content\fP column are indexed
|
@@ -15025,15 +15025,15 @@ command outputs 10 records at a maximum by default. There are only 5
|
|
15025
15025
|
records. It is less than 10. So the command outputs all records.
|
15026
15026
|
.SS Search conditions
|
15027
15027
|
.sp
|
15028
|
-
Search conditions are specified by \fBquery\fP or \fBfilter\fP
|
15029
|
-
also specify both \fBquery\fP and \fBfilter\fP
|
15030
|
-
records must be matched against both \fBquery\fP and \fBfilter\fP
|
15028
|
+
Search conditions are specified by \fBquery\fP or \fBfilter\fP\&. You can
|
15029
|
+
also specify both \fBquery\fP and \fBfilter\fP\&. It means that selected
|
15030
|
+
records must be matched against both \fBquery\fP and \fBfilter\fP\&.
|
15031
15031
|
.SS Search condition: \fBquery\fP
|
15032
15032
|
.sp
|
15033
15033
|
\fBquery\fP is designed for search box in Web page. Imagine a search box
|
15034
15034
|
in google.com. You specify search conditions for \fBquery\fP as space
|
15035
15035
|
separated keywords. For example, \fBsearch engine\fP means a matched
|
15036
|
-
record should contain two words, \fBsearch\fP and \fBengine\fP
|
15036
|
+
record should contain two words, \fBsearch\fP and \fBengine\fP\&.
|
15037
15037
|
.sp
|
15038
15038
|
Normally, \fBquery\fP parameter is used for specifying fulltext search
|
15039
15039
|
conditions. It can be used for non fulltext search conditions but
|
@@ -15042,7 +15042,7 @@ conditions. It can be used for non fulltext search conditions but
|
|
15042
15042
|
\fBquery\fP parameter is used with \fBmatch_columns\fP parameter when
|
15043
15043
|
\fBquery\fP parameter is used for specifying fulltext search
|
15044
15044
|
conditions. \fBmatch_columns\fP specifies which columnes and indexes are
|
15045
|
-
matched against \fBquery\fP
|
15045
|
+
matched against \fBquery\fP\&.
|
15046
15046
|
.sp
|
15047
15047
|
Here is a simple \fBquery\fP usage example.
|
15048
15048
|
.sp
|
@@ -15167,7 +15167,7 @@ select Entries \-\-filter \(aqcontent @ "fast" && _key == "Groonga"\(aq
|
|
15167
15167
|
The \fBselect\fP command searches records that contain a word \fBfast\fP
|
15168
15168
|
in \fBcontent\fP column value and has \fBGroonga\fP as \fB_key\fP from
|
15169
15169
|
\fBEntries\fP table. There are three operators in the command, \fB@\fP,
|
15170
|
-
\fB&&\fP and \fB==\fP
|
15170
|
+
\fB&&\fP and \fB==\fP\&. \fB@\fP is fulltext search operator. \fB&&\fP and
|
15171
15171
|
\fB==\fP are the same as ECMAScript. \fB&&\fP is logical AND operator and
|
15172
15172
|
\fB==\fP is equality operator.
|
15173
15173
|
.sp
|
@@ -15176,7 +15176,7 @@ its deatils aren\(aqt described here. See \fB/reference/grn_expr/script_syntax\f
|
|
15176
15176
|
datails.
|
15177
15177
|
.SS Paging
|
15178
15178
|
.sp
|
15179
|
-
You can specify range of outputted records by \fBoffset\fP and \fBlimit\fP
|
15179
|
+
You can specify range of outputted records by \fBoffset\fP and \fBlimit\fP\&.
|
15180
15180
|
Here is an example to output only the 2nd record.
|
15181
15181
|
.sp
|
15182
15182
|
Execution example:
|
@@ -15291,7 +15291,7 @@ records.
|
|
15291
15291
|
This section describes all parameters. Parameters are categorized.
|
15292
15292
|
.SS Required parameter
|
15293
15293
|
.sp
|
15294
|
-
There is a required parameter, \fBtable\fP
|
15294
|
+
There is a required parameter, \fBtable\fP\&.
|
15295
15295
|
.SS \fBtable\fP
|
15296
15296
|
.sp
|
15297
15297
|
It specifies a table to be searched. \fBtable\fP must be specified.
|
@@ -15332,7 +15332,7 @@ box. \fBfilter\fP parameters is used for implementing complex search
|
|
15332
15332
|
feature.
|
15333
15333
|
.sp
|
15334
15334
|
If both \fBquery\fP and \fBfilter\fP are specified, selected records must
|
15335
|
-
be matched against both \fBquery\fP and \fBfilter\fP
|
15335
|
+
be matched against both \fBquery\fP and \fBfilter\fP\&. If both \fBquery\fP
|
15336
15336
|
and \fBfilter\fP aren\(aqt specified, all records are selected.
|
15337
15337
|
.SS \fBmatch_columns\fP
|
15338
15338
|
.sp
|
@@ -15400,7 +15400,7 @@ records.
|
|
15400
15400
|
.sp
|
15401
15401
|
Pay attention to \fB_score\fP value. \fB_score\fP value is the number of
|
15402
15402
|
matched counts against \fBquery\fP parameter value. In the example,
|
15403
|
-
\fBquery\fP parameter value is \fBfast\fP
|
15403
|
+
\fBquery\fP parameter value is \fBfast\fP\&. The fact that \fB_score\fP value
|
15404
15404
|
is 1 means that \fBfast\fP appers in \fBcontent\fP column only once. The
|
15405
15405
|
fact that \fB_score\fP value is 2 means that \fBfast\fP appears in
|
15406
15406
|
\fBcontent\fP column twice.
|
@@ -15520,11 +15520,11 @@ of blog entry is more important rather thatn content of blog entry.
|
|
15520
15520
|
It specifies the query text. Normally, it is used for fulltext search
|
15521
15521
|
with \fBmatch_columns\fP parameter. \fBquery\fP parameter is designed for
|
15522
15522
|
a fulltext search form in a Web page. A query text should be formatted
|
15523
|
-
in \fB/reference/grn_expr/query_syntax\fP
|
15523
|
+
in \fB/reference/grn_expr/query_syntax\fP\&. The syntax is similar to common search
|
15524
15524
|
form like Google\(aqs search form. For example, \fBword1 word2\fP means
|
15525
15525
|
that groonga searches records that contain both \fBword1\fP and
|
15526
|
-
\fBword2\fP
|
15527
|
-
contain either \fBword1\fP or \fBword2\fP
|
15526
|
+
\fBword2\fP\&. \fBword1 OR word2\fP means that groogna searches records that
|
15527
|
+
contain either \fBword1\fP or \fBword2\fP\&.
|
15528
15528
|
.sp
|
15529
15529
|
Here is a simple logical and search example.
|
15530
15530
|
.sp
|
@@ -15648,8 +15648,8 @@ See \fB/reference/grn_expr/query_syntax\fP for other syntax.
|
|
15648
15648
|
.sp
|
15649
15649
|
It can be used for not only fulltext search but also other
|
15650
15650
|
conditions. For example, \fBcolumn:value\fP means the value of
|
15651
|
-
\fBcolumn\fP column is equal to \fBvalue\fP
|
15652
|
-
value of \fBcolumn\fP column is less than \fBvalue\fP
|
15651
|
+
\fBcolumn\fP column is equal to \fBvalue\fP\&. \fBcolumn:<value\fP means the
|
15652
|
+
value of \fBcolumn\fP column is less than \fBvalue\fP\&.
|
15653
15653
|
.sp
|
15654
15654
|
Here is a simple equality operator search example.
|
15655
15655
|
.sp
|
@@ -15786,14 +15786,14 @@ It specifies the filter text. Normally, it is used for complex search
|
|
15786
15786
|
conditions. \fBfilter\fP can be used with \fBquery\fP parameter. If both
|
15787
15787
|
\fBfilter\fP and \fBquery\fP are specified, there are conbined with
|
15788
15788
|
logical and. It means that matched records should be matched against
|
15789
|
-
both \fBfilter\fP and \fBquery\fP
|
15789
|
+
both \fBfilter\fP and \fBquery\fP\&.
|
15790
15790
|
.sp
|
15791
15791
|
\fBfilter\fP parameter is designed for complex conditions. A filter text
|
15792
|
-
should be formated in \fB/reference/grn_expr/script_syntax\fP
|
15792
|
+
should be formated in \fB/reference/grn_expr/script_syntax\fP\&. The syntax is
|
15793
15793
|
similar to ECMAScript. For example, \fBcolumn == "value"\fP means that
|
15794
|
-
the value of \fBcolumn\fP column is equal to \fB"value"\fP
|
15794
|
+
the value of \fBcolumn\fP column is equal to \fB"value"\fP\&. \fBcolumn <
|
15795
15795
|
value\fP means that the value of \fBcolumn\fP column is less than
|
15796
|
-
\fBvalue\fP
|
15796
|
+
\fBvalue\fP\&.
|
15797
15797
|
.sp
|
15798
15798
|
Here is a simple equality operator search example.
|
15799
15799
|
.sp
|
@@ -16042,9 +16042,9 @@ select Entries \-\-match_columns content \-\-query groo \-\-match_escalation_thr
|
|
16042
16042
|
The first \fBselect\fP command searches records that contain a word
|
16043
16043
|
\fBgroo\fP in \fBcontent\fP column value from \fBEntries\fP table. But no
|
16044
16044
|
records are matched because the \fBTokenBigram\fP tokenizer tokenizes
|
16045
|
-
\fBgroonga\fP to \fBgroonga\fP not \fBgr|ro|oo|on|ng|ga\fP
|
16045
|
+
\fBgroonga\fP to \fBgroonga\fP not \fBgr|ro|oo|on|ng|ga\fP\&. (The
|
16046
16046
|
\fBTokenBigramSplitSymbolAlpha\fP tokenizer tokenizes \fBgroonga\fP to
|
16047
|
-
\fBgr|ro|oo|on|ng|ga\fP
|
16047
|
+
\fBgr|ro|oo|on|ng|ga\fP\&. See \fB/reference/tokenizers\fP for details.)
|
16048
16048
|
It means that \fBgroonga\fP is indexed but \fBgroo\fP isn\(aqt indexed. So no
|
16049
16049
|
records are matched against \fBgroo\fP by exact match. In the case, the
|
16050
16050
|
search storategy escalation is used because the number of matched
|
@@ -16065,7 +16065,7 @@ Deprecated. Use \fIquery\-expander\fP instead.
|
|
16065
16065
|
It customs \fBquery\fP parameter syntax. You cannot update column value
|
16066
16066
|
by \fBquery\fP parameter by default. But if you specify
|
16067
16067
|
\fBALLOW_COLUMN|ALLOW_UPDATE\fP as \fBquery_flags\fP, you can update
|
16068
|
-
column value by \fBquery\fP
|
16068
|
+
column value by \fBquery\fP\&.
|
16069
16069
|
.sp
|
16070
16070
|
Here are available values:
|
16071
16071
|
.INDENT 0.0
|
@@ -16081,11 +16081,11 @@ Here are available values:
|
|
16081
16081
|
\fBNONE\fP
|
16082
16082
|
.UNINDENT
|
16083
16083
|
.sp
|
16084
|
-
\fBALLOW_PRAGMA\fP enables pragma at the head of \fBquery\fP
|
16084
|
+
\fBALLOW_PRAGMA\fP enables pragma at the head of \fBquery\fP\&. This is not
|
16085
16085
|
implemented yet.
|
16086
16086
|
.sp
|
16087
16087
|
\fBALLOW_COLUMN\fP enables search againt columns that are not included
|
16088
|
-
in \fBmatch_columns\fP
|
16088
|
+
in \fBmatch_columns\fP\&. To specify column, there are \fBCOLUMN:...\fP
|
16089
16089
|
syntaxes.
|
16090
16090
|
.sp
|
16091
16091
|
\fBALLOW_UPDATE\fP enables column update by \fBquery\fP with
|
@@ -16094,18 +16094,18 @@ update column because the column update syntax specifies column.
|
|
16094
16094
|
.sp
|
16095
16095
|
\fBALLOW_LEADING_NOT\fP enables leading NOT condition with \fB\-WORD\fP
|
16096
16096
|
syntax. The query searches records that doesn\(aqt match
|
16097
|
-
\fBWORD\fP
|
16097
|
+
\fBWORD\fP\&. Leading NOT condition query is heavy query in many cases
|
16098
16098
|
because it matches many records. So this flag is disabled by
|
16099
16099
|
default. Be careful about it when you use the flag.
|
16100
16100
|
.sp
|
16101
16101
|
\fBNONE\fP is just ignores. You can use \fBNONE\fP for specifying no flags.
|
16102
16102
|
.sp
|
16103
16103
|
They can be combined by separated \fB|\fP such as
|
16104
|
-
\fBALLOW_COLUMN|ALLOW_UPDATE\fP
|
16104
|
+
\fBALLOW_COLUMN|ALLOW_UPDATE\fP\&.
|
16105
16105
|
.sp
|
16106
|
-
The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP
|
16106
|
+
The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP\&.
|
16107
16107
|
.sp
|
16108
|
-
Here is a usage example of \fBALLOW_COLUMN\fP
|
16108
|
+
Here is a usage example of \fBALLOW_COLUMN\fP\&.
|
16109
16109
|
.sp
|
16110
16110
|
Execution example:
|
16111
16111
|
.INDENT 0.0
|
@@ -16160,7 +16160,7 @@ select Entries \-\-query content:@mroonga \-\-query_flags ALLOW_COLUMN
|
|
16160
16160
|
The \fBselect\fP command searches records that contain \fBmroonga\fP in
|
16161
16161
|
\fBcontent\fP column value from \fBEntries\fP table.
|
16162
16162
|
.sp
|
16163
|
-
Here is a usage example of \fBALLOW_UPDATE\fP
|
16163
|
+
Here is a usage example of \fBALLOW_UPDATE\fP\&.
|
16164
16164
|
.sp
|
16165
16165
|
Execution example:
|
16166
16166
|
.INDENT 0.0
|
@@ -16262,10 +16262,10 @@ select Users
|
|
16262
16262
|
.UNINDENT
|
16263
16263
|
.sp
|
16264
16264
|
The first \fBselect\fP command sets \fBage\fP column value of all records
|
16265
|
-
to \fB19\fP
|
16265
|
+
to \fB19\fP\&. The second \fBselect\fP command outputs updated \fBage\fP
|
16266
16266
|
column values.
|
16267
16267
|
.sp
|
16268
|
-
Here is a usage example of \fBALLOW_LEADING_NOT\fP
|
16268
|
+
Here is a usage example of \fBALLOW_LEADING_NOT\fP\&.
|
16269
16269
|
.sp
|
16270
16270
|
Execution example:
|
16271
16271
|
.INDENT 0.0
|
@@ -16338,7 +16338,7 @@ select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALL
|
|
16338
16338
|
The \fBselect\fP command searches records that don\(aqt contain \fBmroonga\fP
|
16339
16339
|
in \fBcontent\fP column value from \fBEntries\fP table.
|
16340
16340
|
.sp
|
16341
|
-
Here is a usage example of \fBNONE\fP
|
16341
|
+
Here is a usage example of \fBNONE\fP\&.
|
16342
16342
|
.sp
|
16343
16343
|
Execution example:
|
16344
16344
|
.INDENT 0.0
|
@@ -16393,10 +16393,10 @@ select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(
|
|
16393
16393
|
The \fBselect\fP command searches records that contain one of two words
|
16394
16394
|
\fBmroonga\fP or \fB_key:Groonga\fP in \fBcontent\fP from \fBEntries\fP table.
|
16395
16395
|
Note that \fB_key:Groonga\fP doesn\(aqt mean that the value of \fB_key\fP
|
16396
|
-
column is equal to \fBGroonga\fP
|
16396
|
+
column is equal to \fBGroonga\fP\&. Because \fBALLOW_COLUMN\fP flag is not
|
16397
16397
|
specified.
|
16398
16398
|
.sp
|
16399
|
-
See also \fB/reference/grn_expr/query_syntax\fP
|
16399
|
+
See also \fB/reference/grn_expr/query_syntax\fP\&.
|
16400
16400
|
.SS \fBquery_expander\fP
|
16401
16401
|
.sp
|
16402
16402
|
It\(aqs for query expansion. Query expansion substitutes specific words
|
@@ -16408,13 +16408,13 @@ value. The format of this parameter value is
|
|
16408
16408
|
\fBsynonym\fP column in \fBTerms\fP table.
|
16409
16409
|
.sp
|
16410
16410
|
Table for query expansion is called "substitution table". Substitution
|
16411
|
-
table\(aqs key must be \fBShortText\fP
|
16411
|
+
table\(aqs key must be \fBShortText\fP\&. So array table (\fBTABLE_NO_KEY\fP)
|
16412
16412
|
can\(aqt be used for query expansion. Because array table doesn\(aqt have
|
16413
16413
|
key.
|
16414
16414
|
.sp
|
16415
16415
|
Column for query expansion is called "substitution
|
16416
16416
|
column". Substitution column\(aqs value type must be
|
16417
|
-
\fBShortText\fP
|
16417
|
+
\fBShortText\fP\&. Column type must be vector (\fBCOLUMN_VECTOR\fP).
|
16418
16418
|
.sp
|
16419
16419
|
Query expansion substitutes key of substitution table in query with
|
16420
16420
|
values in substitution column. If a word in \fBquery\fP is a key of
|
@@ -16448,15 +16448,15 @@ load \-\-table Thesaurus
|
|
16448
16448
|
.UNINDENT
|
16449
16449
|
.sp
|
16450
16450
|
\fBThesaurus\fP substitution table has two synonyms, \fB"mroonga"\fP and
|
16451
|
-
\fB"groonga"\fP
|
16452
|
-
searches with \fB"((mroonga) OR (tritonn) OR (groonga mysql))"\fP
|
16451
|
+
\fB"groonga"\fP\&. If an user searches with \fB"mroonga"\fP, groonga
|
16452
|
+
searches with \fB"((mroonga) OR (tritonn) OR (groonga mysql))"\fP\&. If an
|
16453
16453
|
user searches with \fB"groonga"\fP, groonga searches with \fB"((groonga)
|
16454
|
-
OR (senna))"\fP
|
16454
|
+
OR (senna))"\fP\&. Nomrally, it\(aqs good idea that substitution table has
|
16455
16455
|
\fBKEY_NORMALIZE\fP flag. If the flag is used, substitute target word is
|
16456
16456
|
matched in case insensitive manner.
|
16457
16457
|
.sp
|
16458
16458
|
Note that those synonym values include the key value such as
|
16459
|
-
\fB"mroonga"\fP and \fB"groonga"\fP
|
16459
|
+
\fB"mroonga"\fP and \fB"groonga"\fP\&. It\(aqs recommended that you include the
|
16460
16460
|
key value. If you don\(aqt include key value, substituted value doesn\(aqt
|
16461
16461
|
include the original substitute target value. Normally, including the
|
16462
16462
|
original value is better search result. If you have a word that you
|
@@ -16613,7 +16613,7 @@ third \fBselect\fP command doesn\(aqt use query expansion but it is same as
|
|
16613
16613
|
the second \fBselect\fP command. The third one uses expanded query.
|
16614
16614
|
.sp
|
16615
16615
|
Each substitute value can contain any \fB/reference/grn_expr/query_syntax\fP syntax
|
16616
|
-
such as \fB(...)\fP and \fBOR\fP
|
16616
|
+
such as \fB(...)\fP and \fBOR\fP\&. You can use complex substitution by
|
16617
16617
|
using those syntax.
|
16618
16618
|
.sp
|
16619
16619
|
Here is a complex substitution usage example that uses query syntax.
|
@@ -16679,8 +16679,8 @@ select Entries \-\-match_columns content \-\-query "popular" \-\-query_expander
|
|
16679
16679
|
.UNINDENT
|
16680
16680
|
.UNINDENT
|
16681
16681
|
.sp
|
16682
|
-
The \fBload\fP command registers a new synonym \fB"popular"\fP
|
16683
|
-
substituted with \fB((popular) OR (n_likes:>=10))\fP
|
16682
|
+
The \fBload\fP command registers a new synonym \fB"popular"\fP\&. It is
|
16683
|
+
substituted with \fB((popular) OR (n_likes:>=10))\fP\&. The substituted
|
16684
16684
|
query means that "popular" is containing the word "popular" or 10 or
|
16685
16685
|
more liked entries.
|
16686
16686
|
.sp
|
@@ -16689,7 +16689,7 @@ is equal to or more than \fB10\fP from \fBEntries\fP table.
|
|
16689
16689
|
.SS Output related parameters
|
16690
16690
|
.SS \fBoutput_columns\fP
|
16691
16691
|
.sp
|
16692
|
-
It specifies output columns separated by \fB,\fP
|
16692
|
+
It specifies output columns separated by \fB,\fP\&.
|
16693
16693
|
.sp
|
16694
16694
|
Here is a simple \fBoutput_columns\fP usage example.
|
16695
16695
|
.sp
|
@@ -16737,7 +16737,7 @@ The \fBselect\fP command just outputs \fB_id\fP and \fB_key\fP column
|
|
16737
16737
|
values.
|
16738
16738
|
.sp
|
16739
16739
|
\fB*\fP is a special value. It means that all columns that are not
|
16740
|
-
\fB/reference/pseudo_column\fP
|
16740
|
+
\fB/reference/pseudo_column\fP\&.
|
16741
16741
|
.sp
|
16742
16742
|
Here is a \fB*\fP usage example.
|
16743
16743
|
.sp
|
@@ -16790,11 +16790,11 @@ The \fBselect\fP command outputs \fB_key\fP pseudo column, \fBcontent\fP
|
|
16790
16790
|
column and \fBn_likes\fP column values but doesn\(aqt output \fB_id\fP pseudo
|
16791
16791
|
column value.
|
16792
16792
|
.sp
|
16793
|
-
The default value is \fB_id, _key, *\fP
|
16793
|
+
The default value is \fB_id, _key, *\fP\&. It means that all column
|
16794
16794
|
values except \fB_score\fP are outputted.
|
16795
16795
|
.SS \fBsortby\fP
|
16796
16796
|
.sp
|
16797
|
-
It specifies sort keys separated by \fB,\fP
|
16797
|
+
It specifies sort keys separated by \fB,\fP\&. Each sort key is column
|
16798
16798
|
name.
|
16799
16799
|
.sp
|
16800
16800
|
Here is a simple \fBsortby\fP usage example.
|
@@ -16957,7 +16957,7 @@ select Entries \-\-sortby \(aq\-n_likes, _id\(aq
|
|
16957
16957
|
.UNINDENT
|
16958
16958
|
.sp
|
16959
16959
|
The \fBselect\fP command sorts by \fBn_likes\fP column value in descending
|
16960
|
-
order. But ascending order is used for sorting by \fB_id\fP
|
16960
|
+
order. But ascending order is used for sorting by \fB_id\fP\&.
|
16961
16961
|
.sp
|
16962
16962
|
You can use \fB_score\fP pseudo column in \fBsortby\fP if you use
|
16963
16963
|
\fBquery\fP or \fBfilter\fP parameter.
|
@@ -17058,7 +17058,7 @@ select Entries \-\-sortby _id \-\-offset 3 \-\-output_columns _key
|
|
17058
17058
|
The \fBselect\fP command outputs from the 4th record.
|
17059
17059
|
.sp
|
17060
17060
|
You can specify negative value. It means that \fBthe number of matched
|
17061
|
-
records + offset\fP
|
17061
|
+
records + offset\fP\&. If you have 3 matched records and specify
|
17062
17062
|
\fB\-\-offset \-2\fP, you get records from the 1st (\fB3 + \-2 = 1\fP) record
|
17063
17063
|
to the 3rd record.
|
17064
17064
|
.sp
|
@@ -17101,9 +17101,9 @@ select Entries \-\-sortby _id \-\-offset \-2 \-\-output_columns _key
|
|
17101
17101
|
.UNINDENT
|
17102
17102
|
.sp
|
17103
17103
|
The \fBselect\fP command outputs from the 4th record because the total
|
17104
|
-
number of records is \fB5\fP
|
17104
|
+
number of records is \fB5\fP\&.
|
17105
17105
|
.sp
|
17106
|
-
The default value is \fB0\fP
|
17106
|
+
The default value is \fB0\fP\&.
|
17107
17107
|
.SS \fBlimit\fP
|
17108
17108
|
.sp
|
17109
17109
|
It specifies the max number of output records. If the number of
|
@@ -17155,7 +17155,7 @@ select Entries \-\-sortby _id \-\-offset 2 \-\-limit 3 \-\-output_columns _key
|
|
17155
17155
|
The \fBselect\fP command outputs the 3rd, the 4th and the 5th records.
|
17156
17156
|
.sp
|
17157
17157
|
You can specify negative value. It means that \fBthe number of matched
|
17158
|
-
records + limit + 1\fP
|
17158
|
+
records + limit + 1\fP\&. For example, \fB\-\-limit \-1\fP outputs all
|
17159
17159
|
records. It\(aqs very useful value to show all records.
|
17160
17160
|
.sp
|
17161
17161
|
Here is a simple negative \fBlimit\fP value usage example.
|
@@ -17236,7 +17236,7 @@ select Entries \-\-limit \-1
|
|
17236
17236
|
.sp
|
17237
17237
|
The \fBselect\fP command outputs all records.
|
17238
17238
|
.sp
|
17239
|
-
The default value is \fB10\fP
|
17239
|
+
The default value is \fB10\fP\&.
|
17240
17240
|
.SS \fBscorer\fP
|
17241
17241
|
.sp
|
17242
17242
|
TODO: write in English and add example.
|
@@ -17599,7 +17599,7 @@ The suggest command does suggestion.
|
|
17599
17599
|
.UNINDENT
|
17600
17600
|
.UNINDENT
|
17601
17601
|
.sp
|
17602
|
-
You can specify one or more types separated by \fB|\fP
|
17602
|
+
You can specify one or more types separated by \fB|\fP\&.
|
17603
17603
|
Here are examples:
|
17604
17604
|
.INDENT 7.0
|
17605
17605
|
.INDENT 3.5
|
@@ -17698,7 +17698,7 @@ It specifies number of returned records.
|
|
17698
17698
|
.TP
|
17699
17699
|
.B \fBfrequency_threshold\fP
|
17700
17700
|
It specifies threshold for item frequency. Returned records must have
|
17701
|
-
\fB_score\fP that is greater than or equal to \fBfrequency_threshold\fP
|
17701
|
+
\fB_score\fP that is greater than or equal to \fBfrequency_threshold\fP\&.
|
17702
17702
|
.INDENT 7.0
|
17703
17703
|
.TP
|
17704
17704
|
.B Default:
|
@@ -17714,7 +17714,7 @@ probability. Conditional probability is used for learned
|
|
17714
17714
|
data. It is probability of query submission when \fBquery\fP
|
17715
17715
|
is occurred. Returned records must have conditional
|
17716
17716
|
probability that is greater than or equal to
|
17717
|
-
\fBconditional_probability_threshold\fP
|
17717
|
+
\fBconditional_probability_threshold\fP\&.
|
17718
17718
|
.INDENT 0.0
|
17719
17719
|
.TP
|
17720
17720
|
.B Default:
|
@@ -17802,7 +17802,7 @@ Here is a returned JSON format:
|
|
17802
17802
|
\fBtype\fP
|
17803
17803
|
.INDENT 0.0
|
17804
17804
|
.INDENT 3.5
|
17805
|
-
A type specified by \fBtypes\fP
|
17805
|
+
A type specified by \fBtypes\fP\&.
|
17806
17806
|
.UNINDENT
|
17807
17807
|
.UNINDENT
|
17808
17808
|
.sp
|
@@ -17816,7 +17816,7 @@ A candidate for completion, correction or suggestion.
|
|
17816
17816
|
\fBscore of candidate\fP
|
17817
17817
|
.INDENT 0.0
|
17818
17818
|
.INDENT 3.5
|
17819
|
-
A score of corresponding \fBcandidate\fP
|
17819
|
+
A score of corresponding \fBcandidate\fP\&. It means that
|
17820
17820
|
higher score candidate is more likely candidate for
|
17821
17821
|
completion, correction or suggestion. Returned candidates
|
17822
17822
|
are sorted by \fBscore of candidate\fP descending by
|
@@ -18200,7 +18200,7 @@ table_create Lexicon TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram \
|
|
18200
18200
|
The \fBtable_create\fP command creates the following table:
|
18201
18201
|
.INDENT 0.0
|
18202
18202
|
.IP \(bu 2
|
18203
|
-
The table is named \fBLexicon\fP
|
18203
|
+
The table is named \fBLexicon\fP\&.
|
18204
18204
|
.IP \(bu 2
|
18205
18205
|
The table is \fBTABLE_PAT_KEY\fP type table.
|
18206
18206
|
.IP \(bu 2
|
@@ -18217,14 +18217,14 @@ table is used for fulltext search.
|
|
18217
18217
|
.sp
|
18218
18218
|
In fulltext search, predictive search may be used for fuzzy
|
18219
18219
|
search. Predictive search is supported by \fBTABLE_PAT_KEY\fP and
|
18220
|
-
\fBTABLE_DAT_KEY\fP
|
18220
|
+
\fBTABLE_DAT_KEY\fP\&.
|
18221
18221
|
.sp
|
18222
18222
|
Lexicon table has many keys because a fulltext target text has many
|
18223
18223
|
tokens. Table that has many keys should consider table size because
|
18224
18224
|
large table requires large memory. Requiring large memory causes disk
|
18225
18225
|
I/O. It blocks fast search. So table size is important for a table
|
18226
18226
|
that has many keys. \fBTABLE_PAT_KEY\fP is less table size than
|
18227
|
-
\fBTABLE_DAT_KEY\fP
|
18227
|
+
\fBTABLE_DAT_KEY\fP\&.
|
18228
18228
|
.sp
|
18229
18229
|
Because of the above reasons, \fBTABLE_PAT_KEY\fP is suitable table type
|
18230
18230
|
for lexicon table.
|
@@ -18294,7 +18294,7 @@ suitable. Index for age is the case in the above example. Index for
|
|
18294
18294
|
age will have only 0\-100 items because human doesn\(aqt live so long.
|
18295
18295
|
.sp
|
18296
18296
|
If you have many indexed items, \fBTABLE_PAT_KEY\fP is suitable. Because
|
18297
|
-
\fBTABLE_PAT_KEY\fP is smaller than \fBTABLE_DAT_KEY\fP
|
18297
|
+
\fBTABLE_PAT_KEY\fP is smaller than \fBTABLE_DAT_KEY\fP\&.
|
18298
18298
|
.SS Parameters
|
18299
18299
|
.sp
|
18300
18300
|
This section describes all parameters.
|
@@ -18323,7 +18323,7 @@ character.)
|
|
18323
18323
|
.sp
|
18324
18324
|
You need to create a name with one or more the above chracters. Note
|
18325
18325
|
that you cannot use \fB_\fP as the first character such as
|
18326
|
-
\fB_name\fP
|
18326
|
+
\fB_name\fP\&.
|
18327
18327
|
.SS \fBflags\fP
|
18328
18328
|
.sp
|
18329
18329
|
It specifies a table type and table customize options.
|
@@ -18367,7 +18367,7 @@ T{
|
|
18367
18367
|
\fBKEY_WITH_SIS\fP
|
18368
18368
|
T} T{
|
18369
18369
|
Enable Semi Infinite String.
|
18370
|
-
Require \fBTABLE_PAT_KEY\fP
|
18370
|
+
Require \fBTABLE_PAT_KEY\fP\&.
|
18371
18371
|
T}
|
18372
18372
|
_
|
18373
18373
|
.TE
|
@@ -18385,11 +18385,11 @@ or more \fBTABLE_${TYPE}\fP flags. For example,
|
|
18385
18385
|
\fBTABLE_NO_KEY|TABLE_HASH_KEY\fP is invalid.
|
18386
18386
|
.sp
|
18387
18387
|
You can combine flags with \fB|\fP (vertical bar) such as
|
18388
|
-
\fBTABLE_PAT_KEY|KEY_WITH_SIS\fP
|
18388
|
+
\fBTABLE_PAT_KEY|KEY_WITH_SIS\fP\&.
|
18389
18389
|
.sp
|
18390
18390
|
See \fB/reference/tables\fP for difference between table types.
|
18391
18391
|
.sp
|
18392
|
-
The default flags are \fBTABLE_HASH_KEY\fP
|
18392
|
+
The default flags are \fBTABLE_HASH_KEY\fP\&.
|
18393
18393
|
.SS \fBkey_type\fP
|
18394
18394
|
.sp
|
18395
18395
|
It specifies key type.
|
@@ -18449,9 +18449,9 @@ The default value is none.
|
|
18449
18449
|
.UNINDENT
|
18450
18450
|
.UNINDENT
|
18451
18451
|
.sp
|
18452
|
-
If \fBtable_create\fP fails, error details are in \fBHEADER\fP
|
18452
|
+
If \fBtable_create\fP fails, error details are in \fBHEADER\fP\&.
|
18453
18453
|
.sp
|
18454
|
-
See \fB/reference/command/output_format\fP for \fBHEADER\fP
|
18454
|
+
See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
|
18455
18455
|
.SS See also
|
18456
18456
|
.INDENT 0.0
|
18457
18457
|
.IP \(bu 2
|
@@ -18829,19 +18829,19 @@ tokenize TokenBigram "Fulltext Search"
|
|
18829
18829
|
.UNINDENT
|
18830
18830
|
.sp
|
18831
18831
|
It has only required parameters. \fBtokenizer\fP is \fBTokenBigram\fP and
|
18832
|
-
\fBstring\fP is \fB"Fulltext Search"\fP
|
18832
|
+
\fBstring\fP is \fB"Fulltext Search"\fP\&. It returns tokens that is
|
18833
18833
|
generated by tokenizing \fB"Fulltext Search"\fP with \fBTokenBigram\fP
|
18834
|
-
tokenizer. It doesn\(aqt normalize \fB"Fulltext Search"\fP
|
18834
|
+
tokenizer. It doesn\(aqt normalize \fB"Fulltext Search"\fP\&.
|
18835
18835
|
.SS Parameters
|
18836
18836
|
.sp
|
18837
18837
|
This section describes all parameters. Parameters are categorized.
|
18838
18838
|
.SS Required parameters
|
18839
18839
|
.sp
|
18840
|
-
There are required parameters, \fBtokenizer\fP and \fBstring\fP
|
18840
|
+
There are required parameters, \fBtokenizer\fP and \fBstring\fP\&.
|
18841
18841
|
.SS \fBtokenizer\fP
|
18842
18842
|
.sp
|
18843
18843
|
It specifies the tokenizer name. \fBtokenize\fP command uses the
|
18844
|
-
tokenizer that is named \fBtokenizer\fP
|
18844
|
+
tokenizer that is named \fBtokenizer\fP\&.
|
18845
18845
|
.sp
|
18846
18846
|
See \fB/reference/tokenizers\fP about built\-in tokenizers.
|
18847
18847
|
.sp
|
@@ -18931,7 +18931,7 @@ tokenize TokenTrigram "Fulltext Search"
|
|
18931
18931
|
If you want to use other tokenizers, you need to register additional
|
18932
18932
|
tokenizer plugin by \fBregister\fP command. For example, you can use
|
18933
18933
|
\fI\%KyTea\fP based tokenizer by
|
18934
|
-
registering \fBtokenizers/kytea\fP
|
18934
|
+
registering \fBtokenizers/kytea\fP\&.
|
18935
18935
|
.SS \fBstring\fP
|
18936
18936
|
.sp
|
18937
18937
|
It specifies any string which you want to tokenize.
|
@@ -18939,7 +18939,7 @@ It specifies any string which you want to tokenize.
|
|
18939
18939
|
If you want to include spaces in \fBstring\fP, you need to quote
|
18940
18940
|
\fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
|
18941
18941
|
.sp
|
18942
|
-
Here is an example to use spaces in \fBstring\fP
|
18942
|
+
Here is an example to use spaces in \fBstring\fP\&.
|
18943
18943
|
.sp
|
18944
18944
|
Execution example:
|
18945
18945
|
.INDENT 0.0
|
@@ -19127,8 +19127,8 @@ There are optional parameters.
|
|
19127
19127
|
.SS \fBnormalizer\fP
|
19128
19128
|
.sp
|
19129
19129
|
It specifies the normalizer name. \fBtokenize\fP command uses the
|
19130
|
-
normalizer that is named \fBnormalizer\fP
|
19131
|
-
N\-gram family tokenizers such as \fBTokenBigram\fP
|
19130
|
+
normalizer that is named \fBnormalizer\fP\&. Normalizer is important for
|
19131
|
+
N\-gram family tokenizers such as \fBTokenBigram\fP\&.
|
19132
19132
|
.sp
|
19133
19133
|
Normalizer detects character type for each character while
|
19134
19134
|
normalizing. N\-gram family tokenizers use character types while
|
@@ -19255,7 +19255,7 @@ Continuous alphabets are tokenized as one token. For example,
|
|
19255
19255
|
\fBfulltext\fP is a token.
|
19256
19256
|
.sp
|
19257
19257
|
If you want to tokenize by two characters with noramlizer, use
|
19258
|
-
\fBTokenBigramSplitSymbolAlpha\fP
|
19258
|
+
\fBTokenBigramSplitSymbolAlpha\fP\&.
|
19259
19259
|
.sp
|
19260
19260
|
Execution example:
|
19261
19261
|
.INDENT 0.0
|
@@ -19340,7 +19340,7 @@ to lower case characters. For example, \fBfu\fP is a token.
|
|
19340
19340
|
.sp
|
19341
19341
|
It specifies a tokenization customize options. You can specify
|
19342
19342
|
multiple options separated by "\fB|\fP". For example,
|
19343
|
-
\fBNONE|ENABLE_TOKENIZED_DELIMITER\fP
|
19343
|
+
\fBNONE|ENABLE_TOKENIZED_DELIMITER\fP\&.
|
19344
19344
|
.sp
|
19345
19345
|
Here are available flags.
|
19346
19346
|
.TS
|
@@ -19368,7 +19368,7 @@ T}
|
|
19368
19368
|
_
|
19369
19369
|
.TE
|
19370
19370
|
.sp
|
19371
|
-
Here is an example that uses \fBENABLE_TOKENIZED_DELIMITER\fP
|
19371
|
+
Here is an example that uses \fBENABLE_TOKENIZED_DELIMITER\fP\&.
|
19372
19372
|
.sp
|
19373
19373
|
Execution example:
|
19374
19374
|
.INDENT 0.0
|
@@ -19406,7 +19406,7 @@ tokenize TokenDelimit "Full
|
|
19406
19406
|
\fBTokenDelimit\fP tokenizer is one of tokenized delimiter supported
|
19407
19407
|
tokenizer. \fBENABLE_TOKENIZED_DELIMITER\fP enables tokenized delimiter.
|
19408
19408
|
Tokenized delimiter is special character that indicates token
|
19409
|
-
border. It is \fBU+FFFE\fP
|
19409
|
+
border. It is \fBU+FFFE\fP\&. The character is not assigned any
|
19410
19410
|
character. It means that the character is not appeared in normal
|
19411
19411
|
string. So the character is good character for this puropose. If
|
19412
19412
|
\fBENABLE_TOKENIZED_DELIMITER\fP is enabled, the target string is
|
@@ -19431,7 +19431,7 @@ the feature:
|
|
19431
19431
|
\fBHEADER\fP
|
19432
19432
|
.INDENT 0.0
|
19433
19433
|
.INDENT 3.5
|
19434
|
-
See \fB/reference/command/output_format\fP about \fBHEADER\fP
|
19434
|
+
See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
|
19435
19435
|
.UNINDENT
|
19436
19436
|
.UNINDENT
|
19437
19437
|
.sp
|
@@ -19578,10 +19578,10 @@ select Users
|
|
19578
19578
|
.UNINDENT
|
19579
19579
|
.SS Parameters
|
19580
19580
|
.sp
|
19581
|
-
This section describes parameters of \fBtruncate\fP
|
19581
|
+
This section describes parameters of \fBtruncate\fP\&.
|
19582
19582
|
.SS Required parameter
|
19583
19583
|
.sp
|
19584
|
-
There is required parameter, \fBtable_name\fP
|
19584
|
+
There is required parameter, \fBtable_name\fP\&.
|
19585
19585
|
.SS \fBtable_name\fP
|
19586
19586
|
.sp
|
19587
19587
|
It specifies the name of table.
|
@@ -19776,9 +19776,9 @@ Object型はv1.2でサポートされます。
|
|
19776
19776
|
.SS Tables
|
19777
19777
|
.SS Summary
|
19778
19778
|
.sp
|
19779
|
-
Table in
|
19779
|
+
Table in Groonga manages relation between ID and key. Groonga provides
|
19780
19780
|
four table types. They are \fBTABLE_NO_KEY\fP, \fBTABLE_HASH_KEY\fP,
|
19781
|
-
\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP
|
19781
|
+
\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP\&.
|
19782
19782
|
.sp
|
19783
19783
|
All tables except \fBTABLE_NO_KEY\fP provides both fast ID search by key
|
19784
19784
|
and fast key search by ID. \fBTABLE_NO_KEY\fP doesn\(aqt support
|
@@ -19786,7 +19786,7 @@ key. \fBTABLE_NO_KEY\fP only manages ID. So \fBTABLE_NO_KEY\fP doesn\(aqt
|
|
19786
19786
|
provides ID search and key search.
|
19787
19787
|
.SS Characteristics
|
19788
19788
|
.sp
|
19789
|
-
Here is a chracteristic table of all tables in
|
19789
|
+
Here is a chracteristic table of all tables in Groonga. (\fBTABLE_\fP
|
19790
19790
|
prefix is omitted in the table.)
|
19791
19791
|
.TS
|
19792
19792
|
center;
|
@@ -19994,10 +19994,10 @@ index for range search.
|
|
19994
19994
|
is not suitable for storing many records. \fBTABLE_DAT_KEY\fP is a only
|
19995
19995
|
table that supports key update.
|
19996
19996
|
.sp
|
19997
|
-
\fBTABLE_DAT_KEY\fP is used in
|
19997
|
+
\fBTABLE_DAT_KEY\fP is used in Groonga database. Groonga database needs
|
19998
19998
|
to convert object name such as \fBShortText\fP, \fBTokenBigram\fP and
|
19999
|
-
table names to object ID. And
|
20000
|
-
name. Those features are implemented by \fBTABLE_DAT_KEY\fP
|
19999
|
+
table names to object ID. And Groonga database needs to rename object
|
20000
|
+
name. Those features are implemented by \fBTABLE_DAT_KEY\fP\&. The number
|
20001
20001
|
of objects is small. So large data size demerit of \fBTABLE_DAT_KEY\fP
|
20002
20002
|
can be ignored.
|
20003
20003
|
.SS Record ID
|
@@ -20057,7 +20057,7 @@ normalization by registering your normalizer plugins to Groonga.
|
|
20057
20057
|
A normalizer module is attached to a table. A table can have zero or
|
20058
20058
|
one normalizer module. You can attach a normalizer module to a table
|
20059
20059
|
by \fItable\-create\-normalizer\fP option in
|
20060
|
-
\fB/reference/commands/table_create\fP
|
20060
|
+
\fB/reference/commands/table_create\fP\&.
|
20061
20061
|
.sp
|
20062
20062
|
Here is an example \fBtable_create\fP that uses \fBNormalizerAuto\fP
|
20063
20063
|
normalizer module:
|
@@ -20079,7 +20079,7 @@ table_create Dictionary TABLE_HASH_KEY ShortText \-\-normalizer NormalizerAuto
|
|
20079
20079
|
.INDENT 0.0
|
20080
20080
|
.INDENT 3.5
|
20081
20081
|
Groonga 2.0.9 or earlier doesn\(aqt have \fB\-\-normalizer\fP option in
|
20082
|
-
\fBtable_create\fP
|
20082
|
+
\fBtable_create\fP\&. \fBKEY_NORMALIZE\fP flag was used instead.
|
20083
20083
|
.sp
|
20084
20084
|
You can open an old database by Groonga 2.1.0 or later. An old
|
20085
20085
|
database means that the database is created by Groonga 2.0.9 or
|
@@ -20152,7 +20152,7 @@ select Dictionary
|
|
20152
20152
|
\fBNormalizerAuto\fP normalizer normalizes a text as a downcased text.
|
20153
20153
|
For example, \fB"Apple"\fP is normalized to \fB"apple"\fP, \fB"black"\fP is
|
20154
20154
|
normalized to \fB"blank"\fP and \fB"COLOR"\fP is normalized to
|
20155
|
-
\fB"color"\fP
|
20155
|
+
\fB"color"\fP\&.
|
20156
20156
|
.sp
|
20157
20157
|
If a table is a lexicon for fulltext search, tokenized tokens are
|
20158
20158
|
normalized. Because tokens are stored as table keys. Table keys are
|
@@ -20245,7 +20245,7 @@ Here is a list of additional normalizers provided by \fBgroonga\-normalizer\-mys
|
|
20245
20245
|
.sp
|
20246
20246
|
\fBgroonga\-normalizer\-mysql\fP is a Groonga plugin.
|
20247
20247
|
It provides MySQL compatible normalizers to Groonga.
|
20248
|
-
\fBNormalizerMySQLGeneralCI\fP corresponds to \fButf8mb4_general_ci\fP
|
20248
|
+
\fBNormalizerMySQLGeneralCI\fP corresponds to \fButf8mb4_general_ci\fP\&.
|
20249
20249
|
.sp
|
20250
20250
|
You need to register \fBnormalizers/mysql\fP plugin in advance.
|
20251
20251
|
.sp
|
@@ -20322,7 +20322,7 @@ feature than the embedded query expansion feature. For example, it
|
|
20322
20322
|
doesn\(aqt support word normalization. But it may be easy to use because
|
20323
20323
|
you can manage your synonyms by TSV file. You can edit your synonyms
|
20324
20324
|
by spreadsheet application such as Excel. With the embedded query
|
20325
|
-
expansion feature, you manage your synonyms by
|
20325
|
+
expansion feature, you manage your synonyms by Groonga\(aqs table.
|
20326
20326
|
.SS Install
|
20327
20327
|
.sp
|
20328
20328
|
You need to register \fBquery_expanders/tsv\fP as a plugin before you
|
@@ -20385,9 +20385,9 @@ _
|
|
20385
20385
|
.TE
|
20386
20386
|
.sp
|
20387
20387
|
The table means that \fBsynonym 1\fP and \fBsynonym 2\fP are synonyms of
|
20388
|
-
\fBword\fP
|
20389
|
-
\fBgroonga\fP
|
20390
|
-
\fBmroonga\fP
|
20388
|
+
\fBword\fP\&. For example, \fBgroonga\fP and \fBSenna\fP are synonyms of
|
20389
|
+
\fBgroonga\fP\&. And \fBmroonga\fP and \fBgroonga MySQL\fP are synonyms of
|
20390
|
+
\fBmroonga\fP\&.
|
20391
20391
|
.sp
|
20392
20392
|
Here is an example of query expnasion that uses \fBgroonga\fP as query:
|
20393
20393
|
.INDENT 0.0
|
@@ -20526,12 +20526,12 @@ With the above command, \fB/tmp/synonyms.tsv\fP file is used.
|
|
20526
20526
|
You can define zero or more synonyms in a TSV file. You define a
|
20527
20527
|
\fBword\fP and \fBsynonyms\fP pair by a line. \fBword\fP is expanded to
|
20528
20528
|
\fBsynonyms\fP in \fB\-\-query\fP value. \fBSynonyms\fP are combined by
|
20529
|
-
\fBOR\fP
|
20530
|
-
as \fBgroonga OR Senna\fP
|
20529
|
+
\fBOR\fP\&. For example, \fBgroonga\fP and \fBSenna\fP synonyms are expanded
|
20530
|
+
as \fBgroonga OR Senna\fP\&.
|
20531
20531
|
.sp
|
20532
20532
|
The first column is \fBword\fP and the rest columns are \fBsynonyms\fP of
|
20533
|
-
the \fBword\fP
|
20534
|
-
\fBsynonyms\fP are \fBgroonga\fP and \fBSenna\fP
|
20533
|
+
the \fBword\fP\&. Here is a sample line for \fBword\fP is \fBgroonga\fP and
|
20534
|
+
\fBsynonyms\fP are \fBgroonga\fP and \fBSenna\fP\&. \fB(TAB)\fP means a tab
|
20535
20535
|
character (\fBU+0009\fP):
|
20536
20536
|
.INDENT 0.0
|
20537
20537
|
.INDENT 3.5
|
@@ -20577,7 +20577,7 @@ loaded only at the plugin load time.
|
|
20577
20577
|
疑似カラム
|
20578
20578
|
.SS 説明
|
20579
20579
|
.sp
|
20580
|
-
|
20580
|
+
Groongaのデータベースで作成したテーブルには、いくつかのカラムが自動的に定義されます。
|
20581
20581
|
.sp
|
20582
20582
|
これらのカラムはいずれもアンダースコア(\(aq_\(aq)で始まる名前が付与されます。定義される疑似カラムは、テーブルの種類によって異なります。
|
20583
20583
|
.sp
|
@@ -20620,12 +20620,12 @@ groongaのデータベースで作成したテーブルには、いくつかの
|
|
20620
20620
|
.SS grn_expr
|
20621
20621
|
.sp
|
20622
20622
|
Grn_expr is an object that searches records with specified conditions
|
20623
|
-
and manipulates a database. It\(aqs pronounced as \fBgurun expression\fP
|
20623
|
+
and manipulates a database. It\(aqs pronounced as \fBgurun expression\fP\&.
|
20624
20624
|
.sp
|
20625
20625
|
Conditions for searching records from a database can be represented by
|
20626
20626
|
conbining condition expressions such as \fBequal condition expression\fP
|
20627
20627
|
and \fBless than condition expression\fP with set operations such as
|
20628
|
-
\fBAND\fP, \fBOR\fP and \fBNOT\fP
|
20628
|
+
\fBAND\fP, \fBOR\fP and \fBNOT\fP\&. Grn_expr executes those conditions to
|
20629
20629
|
search records. You can also use advanced searches such as similar
|
20630
20630
|
search and near search by grn_expr. You can also use flexible full
|
20631
20631
|
text search. For example, you can control hit scores for specified
|
@@ -20650,40 +20650,40 @@ Calling grn_expr related APIs.
|
|
20650
20650
|
\fB/reference/grn_expr/query_syntax\fP is for common search form in
|
20651
20651
|
Internet search site. It\(aqs simple and easy to use but it has a
|
20652
20652
|
limitation. You can not use all condition expressions and set
|
20653
|
-
operations in \fB/reference/grn_expr/query_syntax\fP
|
20653
|
+
operations in \fB/reference/grn_expr/query_syntax\fP\&. You can use
|
20654
20654
|
\fB/reference/grn_expr/query_syntax\fP with \fBquery\fP option in
|
20655
|
-
\fB/reference/commands/select\fP
|
20655
|
+
\fB/reference/commands/select\fP\&.
|
20656
20656
|
.sp
|
20657
20657
|
\fB/reference/grn_expr/script_syntax\fP is ECMAScript like
|
20658
20658
|
syntax. You can use all condition expresssions and set operations in
|
20659
|
-
\fB/reference/grn_expr/script_syntax\fP
|
20659
|
+
\fB/reference/grn_expr/script_syntax\fP\&. You can use
|
20660
20660
|
\fB/reference/grn_expr/script_syntax\fP with \fBfilter\fP option and
|
20661
|
-
\fBscorer\fP option in \fB/reference/commands/select\fP
|
20661
|
+
\fBscorer\fP option in \fB/reference/commands/select\fP\&.
|
20662
20662
|
.sp
|
20663
20663
|
You can use groonga as a library and create a grn_expr by calling
|
20664
20664
|
grn_expr related APIs. You can use full features with calling APIs
|
20665
|
-
like \fB/reference/grn_expr/script_syntax\fP
|
20665
|
+
like \fB/reference/grn_expr/script_syntax\fP\&. Calling APIs is useful
|
20666
20666
|
creating a custom syntax to create grn_expr. They are used in \fI\%rroonga\fP that is Ruby bindings
|
20667
|
-
of
|
20667
|
+
of Groonga. Rroonga can create a grn_expr by Ruby\(aqs syntax instead of
|
20668
20668
|
parsing string.
|
20669
20669
|
.SS Query syntax
|
20670
20670
|
.sp
|
20671
20671
|
Query syntax is a syntax to specify search condition for common Web
|
20672
20672
|
search form. It is similar to the syntax of Google\(aqs search form. For
|
20673
20673
|
example, \fBword1 word2\fP means that groonga searches records that
|
20674
|
-
contain both \fBword1\fP and \fBword2\fP
|
20675
|
-
groogna searches records that contain either \fBword1\fP or \fBword2\fP
|
20674
|
+
contain both \fBword1\fP and \fBword2\fP\&. \fBword1 OR word2\fP means that
|
20675
|
+
groogna searches records that contain either \fBword1\fP or \fBword2\fP\&.
|
20676
20676
|
.sp
|
20677
20677
|
Query syntax consists of \fBconditional expression\fP, \fBcombind
|
20678
|
-
expression\fP and \fBassignment expression\fP
|
20678
|
+
expression\fP and \fBassignment expression\fP\&. Nomrally \fBassignment
|
20679
20679
|
expression\fP can be ignored. Because \fBassignment expression\fP is
|
20680
|
-
disabled in \fB\-\-query\fP option of \fB/reference/commands/select\fP
|
20680
|
+
disabled in \fB\-\-query\fP option of \fB/reference/commands/select\fP\&. You can use
|
20681
20681
|
it if you use groonga as library and customize query syntax parser
|
20682
20682
|
options.
|
20683
20683
|
.sp
|
20684
20684
|
\fBConditinal expression\fP specifies an condition. \fBCombinded
|
20685
20685
|
expression\fP consists of one or more \fBconditional expression\fP,
|
20686
|
-
\fBcombined expression\fP or \fBassignment expression\fP
|
20686
|
+
\fBcombined expression\fP or \fBassignment expression\fP\&. \fBAssignment
|
20687
20687
|
expression\fP can assigns a column to a value.
|
20688
20688
|
.SS Sample data
|
20689
20689
|
.sp
|
@@ -20733,7 +20733,7 @@ load \-\-table Entries
|
|
20733
20733
|
.sp
|
20734
20734
|
There is a table, \fBEntries\fP, for blog entries. An entry has title,
|
20735
20735
|
content and the number of likes for the entry. Title is key of
|
20736
|
-
\fBEntries\fP
|
20736
|
+
\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
|
20737
20737
|
number of likes is value of \fBEntries.n_likes\fP column.
|
20738
20738
|
.sp
|
20739
20739
|
\fBEntries._key\fP column and \fBEntries.content\fP column are indexed
|
@@ -20744,8 +20744,8 @@ OK. The schema and data for examples are ready.
|
|
20744
20744
|
.SS Escape
|
20745
20745
|
.sp
|
20746
20746
|
There are special characters in query syntax. To use a special
|
20747
|
-
character as itself, it should be escaped by prepending \fB\e\fP
|
20748
|
-
example, \fB"\fP is a special character. It is escaped as \fB\e"\fP
|
20747
|
+
character as itself, it should be escaped by prepending \fB\e\fP\&. For
|
20748
|
+
example, \fB"\fP is a special character. It is escaped as \fB\e"\fP\&.
|
20749
20749
|
.sp
|
20750
20750
|
Here is a special character list:
|
20751
20751
|
.INDENT 0.0
|
@@ -20754,7 +20754,7 @@ Here is a special character list:
|
|
20754
20754
|
.IP \(bu 2
|
20755
20755
|
\fB[space]\fP (escaped as \fB[backslash][space]\fP) (You should
|
20756
20756
|
substitute \fB[space]\fP with a white space character that is 0x20
|
20757
|
-
in ASCII and \fB[backslash]\fP with \fB\e\e\fP
|
20757
|
+
in ASCII and \fB[backslash]\fP with \fB\e\e\fP\&.)
|
20758
20758
|
.IP \(bu 2
|
20759
20759
|
\fB"\fP (escaped as \fB\e"\fP)
|
20760
20760
|
.IP \(bu 2
|
@@ -20770,10 +20770,10 @@ in ASCII and \fB[backslash]\fP with \fB\e\e\fP.)
|
|
20770
20770
|
.UNINDENT
|
20771
20771
|
.sp
|
20772
20772
|
You can use quote instead of escape. Quote syntax is \fB"..."\fP or
|
20773
|
-
\fB\(aq...\(aq\fP
|
20773
|
+
\fB\(aq...\(aq\fP\&. You need escape \fB"\fP as \fB\e"\fP in \fB"..."\fP quote syntax.
|
20774
20774
|
You need escape \fB\(aq\fP as \fB\e\(aq\fP in \fB\(aq...\(aq\fP quote syntax. For
|
20775
20775
|
example, \fBAlice\(aqs brother (Bob)\fP can be quoted \fB"Alice\(aqs brother
|
20776
|
-
(Bob)"\fP or \fB\(aqAlice\e\(aqs brother (Bob)\(aq\fP
|
20776
|
+
(Bob)"\fP or \fB\(aqAlice\e\(aqs brother (Bob)\(aq\fP\&.
|
20777
20777
|
.sp
|
20778
20778
|
\fBNOTE:\fP
|
20779
20779
|
.INDENT 0.0
|
@@ -20792,7 +20792,7 @@ special character is escaped properly.
|
|
20792
20792
|
Here is available conditional expression list.
|
20793
20793
|
.SS Full text search condition
|
20794
20794
|
.sp
|
20795
|
-
Its syntax is \fBkeyword\fP
|
20795
|
+
Its syntax is \fBkeyword\fP\&.
|
20796
20796
|
.sp
|
20797
20797
|
\fBFull text search condition\fP specifies a full text search condition
|
20798
20798
|
against the default match columns. Match columns are full text search
|
@@ -20800,13 +20800,13 @@ target columns.
|
|
20800
20800
|
.sp
|
20801
20801
|
You should specify the default match columns for full text
|
20802
20802
|
search. They can be specified by \fB\-\-match_columns\fP option of
|
20803
|
-
\fB/reference/commands/select\fP
|
20803
|
+
\fB/reference/commands/select\fP\&. If you don\(aqt specify the default match
|
20804
20804
|
columns, this conditional expression fails.
|
20805
20805
|
.sp
|
20806
20806
|
This conditional expression does full text search with
|
20807
|
-
\fBkeyword\fP
|
20807
|
+
\fBkeyword\fP\&. \fBkeyword\fP should not contain any spaces. If \fBkeyword\fP
|
20808
20808
|
contains a space such as \fBsearch keyword\fP, it means two full text
|
20809
|
-
search conditions; \fBsearch\fP and \fBkeyword\fP
|
20809
|
+
search conditions; \fBsearch\fP and \fBkeyword\fP\&. If you want to
|
20810
20810
|
specifies a keyword that contains one or more spaces, you can use
|
20811
20811
|
\fBphrase search condition\fP that is described below.
|
20812
20812
|
.sp
|
@@ -20874,18 +20874,18 @@ The expression matches records that contain a word \fBfast\fP in
|
|
20874
20874
|
\fBcontent\fP column is the default match column.
|
20875
20875
|
.SS Phrase search condition
|
20876
20876
|
.sp
|
20877
|
-
Its syntax is \fB"search keyword"\fP
|
20877
|
+
Its syntax is \fB"search keyword"\fP\&.
|
20878
20878
|
.sp
|
20879
20879
|
\fBPhrase search condition\fP specifies a phrase search condition
|
20880
20880
|
against the default match columns.
|
20881
20881
|
.sp
|
20882
20882
|
You should specify the default match columns for full text
|
20883
20883
|
search. They can be specified by \fB\-\-match_columns\fP option of
|
20884
|
-
\fB/reference/commands/select\fP
|
20884
|
+
\fB/reference/commands/select\fP\&. If you don\(aqt specify the default match
|
20885
20885
|
columns, this conditional expression fails.
|
20886
20886
|
.sp
|
20887
20887
|
This conditional expression does phrase search with \fBsearch
|
20888
|
-
keyword\fP
|
20888
|
+
keyword\fP\&. Phrase search searches records that contain \fBsearch\fP and
|
20889
20889
|
\fBkeyword\fP and those terms are appeared in the same order and
|
20890
20890
|
adjacent. Thus, \fBPut a search keyword in the form\fP is matched but
|
20891
20891
|
\fBSearch by the keyword\fP and \fBThere is a keyword. Search by it!\fP
|
@@ -20950,12 +20950,12 @@ The expression matches records that contain a phrase \fBI started\fP in
|
|
20950
20950
|
\fBcontent\fP column is the default match column.
|
20951
20951
|
.SS Full text search condition (with explicit match column)
|
20952
20952
|
.sp
|
20953
|
-
Its syntax is \fBcolumn:@keyword\fP
|
20953
|
+
Its syntax is \fBcolumn:@keyword\fP\&.
|
20954
20954
|
.sp
|
20955
20955
|
It\(aqs similar to \fBfull text search condition\fP but it doesn\(aqt require
|
20956
20956
|
the default match columns. You need to specify match column for the
|
20957
20957
|
full text search condition by \fBcolumn:\fP instead of
|
20958
|
-
\fB\-\-match_columns\fP option of \fB/reference/commands/select\fP
|
20958
|
+
\fB\-\-match_columns\fP option of \fB/reference/commands/select\fP\&.
|
20959
20959
|
.sp
|
20960
20960
|
This condtional expression is useful when you want to use two or more
|
20961
20961
|
full text search against different columns. The default match columns
|
@@ -21047,17 +21047,17 @@ The expression matches records that contain a word \fBfast\fP in
|
|
21047
21047
|
\fBcontent\fP column value.
|
21048
21048
|
.SS Phrase search condition (with explicit match column)
|
21049
21049
|
.sp
|
21050
|
-
Its syntax is \fBcolumn:@"search keyword"\fP
|
21050
|
+
Its syntax is \fBcolumn:@"search keyword"\fP\&.
|
21051
21051
|
.sp
|
21052
21052
|
It\(aqs similar to \fBphrase search condition\fP but it doesn\(aqt require the
|
21053
21053
|
default match columns. You need to specify match column for the phrase
|
21054
21054
|
search condition by \fBcolumn:\fP instead of \fB\-\-match_columns\fP option
|
21055
|
-
of \fB/reference/commands/select\fP
|
21055
|
+
of \fB/reference/commands/select\fP\&.
|
21056
21056
|
.sp
|
21057
21057
|
The different between \fBphrase search condition\fP and \fBphrase search
|
21058
21058
|
condition (with explicit match column)\fP is similar to between \fBfull
|
21059
21059
|
text search condition\fP and \fBfull text search condition (with
|
21060
|
-
explicit match column)\fP
|
21060
|
+
explicit match column)\fP\&. \fBPhrase search condition\fP supports
|
21061
21061
|
advanced match columns but \fBphrase search condition (with explicit
|
21062
21062
|
match column)\fP isn\(aqt supported. See description of \fBfull text search
|
21063
21063
|
condition (with explicit match column)\fP about advanced match columns.
|
@@ -21119,24 +21119,24 @@ The expression matches records that contain a phrase \fBI started\fP in
|
|
21119
21119
|
\fBI\fP and \fBstarted\fP aren\(aqt adjacent.
|
21120
21120
|
.SS Prefix search condition
|
21121
21121
|
.sp
|
21122
|
-
Its syntax is \fBcolumn:^value\fP or \fBvalue*\fP
|
21122
|
+
Its syntax is \fBcolumn:^value\fP or \fBvalue*\fP\&.
|
21123
21123
|
.sp
|
21124
|
-
This conditional expression does prefix search with \fBvalue\fP
|
21125
|
-
search searches records that contain a word that starts with \fBvalue\fP
|
21124
|
+
This conditional expression does prefix search with \fBvalue\fP\&. Prefix
|
21125
|
+
search searches records that contain a word that starts with \fBvalue\fP\&.
|
21126
21126
|
.sp
|
21127
21127
|
You can use fast prefix search against a column. The column must be
|
21128
21128
|
indexed and index table must be patricia trie table
|
21129
21129
|
(\fBTABLE_PAT_KEY\fP) or double array trie table
|
21130
21130
|
(\fBTABLE_DAT_KEY\fP). You can also use fast prefix search against
|
21131
21131
|
\fB_key\fP pseudo column of patricia trie table or double array trie
|
21132
|
-
table. You don\(aqt need to index \fB_key\fP
|
21132
|
+
table. You don\(aqt need to index \fB_key\fP\&.
|
21133
21133
|
.sp
|
21134
21134
|
Prefix search can be used with other table types but it causes all
|
21135
21135
|
records scan. It\(aqs not problem for small records but it spends more
|
21136
21136
|
time for large records.
|
21137
21137
|
.sp
|
21138
21138
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21139
|
-
search condition\fP and \fBphrase search condition\fP
|
21139
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21140
21140
|
.sp
|
21141
21141
|
Here is a simple exmaple.
|
21142
21142
|
.sp
|
@@ -21201,17 +21201,17 @@ The expression matches records that contain a word that starts with
|
|
21201
21201
|
\fBGood\-bye Tritonn\fP are matched with the expression.
|
21202
21202
|
.SS Suffix search condition
|
21203
21203
|
.sp
|
21204
|
-
Its syntax is \fBcolumn:$value\fP
|
21204
|
+
Its syntax is \fBcolumn:$value\fP\&.
|
21205
21205
|
.sp
|
21206
|
-
This conditional expression does suffix search with \fBvalue\fP
|
21207
|
-
search searches records that contain a word that ends with \fBvalue\fP
|
21206
|
+
This conditional expression does suffix search with \fBvalue\fP\&. Suffix
|
21207
|
+
search searches records that contain a word that ends with \fBvalue\fP\&.
|
21208
21208
|
.sp
|
21209
21209
|
You can use fast suffix search against a column. The column must be
|
21210
21210
|
indexed and index table must be patricia trie table
|
21211
21211
|
(\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You can also use fast
|
21212
21212
|
suffix search against \fB_key\fP pseudo column of patricia trie table
|
21213
21213
|
(\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You don\(aqt need to
|
21214
|
-
index \fB_key\fP
|
21214
|
+
index \fB_key\fP\&. We recommended that you use index column based fast
|
21215
21215
|
suffix search instead of \fB_key\fP based fast suffix search. \fB_key\fP
|
21216
21216
|
based fast suffix search returns automatically registered
|
21217
21217
|
substrings. (TODO: write document about suffix search and link to it
|
@@ -21232,7 +21232,7 @@ scan. It\(aqs not problem for small records but it spends more time for
|
|
21232
21232
|
large records.
|
21233
21233
|
.sp
|
21234
21234
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21235
|
-
search condition\fP and \fBphrase search condition\fP
|
21235
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21236
21236
|
.sp
|
21237
21237
|
Here is a simple exmaple. It uses fast suffix search for hiragana in
|
21238
21238
|
Japanese that is one of non\-ASCII characters.
|
@@ -21302,12 +21302,12 @@ in \fBcontent\fP column value. \fBぐるんが\fP and \fBむるんが\fP are mat
|
|
21302
21302
|
with the expression.
|
21303
21303
|
.SS Equal condition
|
21304
21304
|
.sp
|
21305
|
-
Its syntax is \fBcolumn:value\fP
|
21305
|
+
Its syntax is \fBcolumn:value\fP\&.
|
21306
21306
|
.sp
|
21307
|
-
It matches records that \fBcolumn\fP value is equal to \fBvalue\fP
|
21307
|
+
It matches records that \fBcolumn\fP value is equal to \fBvalue\fP\&.
|
21308
21308
|
.sp
|
21309
21309
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21310
|
-
search condition\fP and \fBphrase search condition\fP
|
21310
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21311
21311
|
.sp
|
21312
21312
|
Here is a simple exmaple.
|
21313
21313
|
.sp
|
@@ -21362,15 +21362,15 @@ select Entries \-\-query _key:Groonga
|
|
21362
21362
|
.UNINDENT
|
21363
21363
|
.sp
|
21364
21364
|
The expression matches records that \fB_key\fP column value is
|
21365
|
-
equal to \fBGroonga\fP
|
21365
|
+
equal to \fBGroonga\fP\&.
|
21366
21366
|
.SS Not equal condition
|
21367
21367
|
.sp
|
21368
|
-
Its syntax is \fBcolumn:!value\fP
|
21368
|
+
Its syntax is \fBcolumn:!value\fP\&.
|
21369
21369
|
.sp
|
21370
|
-
It matches records that \fBcolumn\fP value isn\(aqt equal to \fBvalue\fP
|
21370
|
+
It matches records that \fBcolumn\fP value isn\(aqt equal to \fBvalue\fP\&.
|
21371
21371
|
.sp
|
21372
21372
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21373
|
-
search condition\fP and \fBphrase search condition\fP
|
21373
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21374
21374
|
.sp
|
21375
21375
|
Here is a simple exmaple.
|
21376
21376
|
.sp
|
@@ -21443,12 +21443,12 @@ select Entries \-\-query _key:!Groonga
|
|
21443
21443
|
.UNINDENT
|
21444
21444
|
.sp
|
21445
21445
|
The expression matches records that \fB_key\fP column value is not equal
|
21446
|
-
to \fBGroonga\fP
|
21446
|
+
to \fBGroonga\fP\&.
|
21447
21447
|
.SS Less than condition
|
21448
21448
|
.sp
|
21449
|
-
Its syntax is \fBcolumn:<value\fP
|
21449
|
+
Its syntax is \fBcolumn:<value\fP\&.
|
21450
21450
|
.sp
|
21451
|
-
It matches records that \fBcolumn\fP value is less than \fBvalue\fP
|
21451
|
+
It matches records that \fBcolumn\fP value is less than \fBvalue\fP\&.
|
21452
21452
|
.sp
|
21453
21453
|
If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
|
21454
21454
|
value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
|
@@ -21456,7 +21456,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
|
|
21456
21456
|
compared as bit sequence.
|
21457
21457
|
.sp
|
21458
21458
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21459
|
-
search condition\fP and \fBphrase search condition\fP
|
21459
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21460
21460
|
.sp
|
21461
21461
|
Here is a simple exmaple.
|
21462
21462
|
.sp
|
@@ -21523,12 +21523,12 @@ select Entries \-\-query n_likes:<10
|
|
21523
21523
|
.UNINDENT
|
21524
21524
|
.sp
|
21525
21525
|
The expression matches records that \fBn_likes\fP column value is less
|
21526
|
-
than \fB10\fP
|
21526
|
+
than \fB10\fP\&.
|
21527
21527
|
.SS Greater than condition
|
21528
21528
|
.sp
|
21529
|
-
Its syntax is \fBcolumn:>value\fP
|
21529
|
+
Its syntax is \fBcolumn:>value\fP\&.
|
21530
21530
|
.sp
|
21531
|
-
It matches records that \fBcolumn\fP value is greater than \fBvalue\fP
|
21531
|
+
It matches records that \fBcolumn\fP value is greater than \fBvalue\fP\&.
|
21532
21532
|
.sp
|
21533
21533
|
If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
|
21534
21534
|
value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
|
@@ -21536,7 +21536,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
|
|
21536
21536
|
compared as bit sequence.
|
21537
21537
|
.sp
|
21538
21538
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21539
|
-
search condition\fP and \fBphrase search condition\fP
|
21539
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21540
21540
|
.sp
|
21541
21541
|
Here is a simple exmaple.
|
21542
21542
|
.sp
|
@@ -21591,13 +21591,13 @@ select Entries \-\-query n_likes:>10
|
|
21591
21591
|
.UNINDENT
|
21592
21592
|
.sp
|
21593
21593
|
The expression matches records that \fBn_likes\fP column value is greater
|
21594
|
-
than \fB10\fP
|
21594
|
+
than \fB10\fP\&.
|
21595
21595
|
.SS Less than or equal to condition
|
21596
21596
|
.sp
|
21597
|
-
Its syntax is \fBcolumn:<=value\fP
|
21597
|
+
Its syntax is \fBcolumn:<=value\fP\&.
|
21598
21598
|
.sp
|
21599
21599
|
It matches records that \fBcolumn\fP value is less than or equal to
|
21600
|
-
\fBvalue\fP
|
21600
|
+
\fBvalue\fP\&.
|
21601
21601
|
.sp
|
21602
21602
|
If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
|
21603
21603
|
value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
|
@@ -21605,7 +21605,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
|
|
21605
21605
|
compared as bit sequence.
|
21606
21606
|
.sp
|
21607
21607
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21608
|
-
search condition\fP and \fBphrase search condition\fP
|
21608
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21609
21609
|
.sp
|
21610
21610
|
Here is a simple exmaple.
|
21611
21611
|
.sp
|
@@ -21678,13 +21678,13 @@ select Entries \-\-query n_likes:<=10
|
|
21678
21678
|
.UNINDENT
|
21679
21679
|
.sp
|
21680
21680
|
The expression matches records that \fBn_likes\fP column value is less
|
21681
|
-
than or equal to \fB10\fP
|
21681
|
+
than or equal to \fB10\fP\&.
|
21682
21682
|
.SS Greater than or equal to condition
|
21683
21683
|
.sp
|
21684
|
-
Its syntax is \fBcolumn:>=value\fP
|
21684
|
+
Its syntax is \fBcolumn:>=value\fP\&.
|
21685
21685
|
.sp
|
21686
21686
|
It matches records that \fBcolumn\fP value is greater than or equal to
|
21687
|
-
\fBvalue\fP
|
21687
|
+
\fBvalue\fP\&.
|
21688
21688
|
.sp
|
21689
21689
|
If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
|
21690
21690
|
value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
|
@@ -21692,7 +21692,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
|
|
21692
21692
|
compared as bit sequence.
|
21693
21693
|
.sp
|
21694
21694
|
It doesn\(aqt require the default match columns such as \fBfull text
|
21695
|
-
search condition\fP and \fBphrase search condition\fP
|
21695
|
+
search condition\fP and \fBphrase search condition\fP\&.
|
21696
21696
|
.sp
|
21697
21697
|
Here is a simple exmaple.
|
21698
21698
|
.sp
|
@@ -21753,13 +21753,13 @@ select Entries \-\-query n_likes:>=10
|
|
21753
21753
|
.UNINDENT
|
21754
21754
|
.sp
|
21755
21755
|
The expression matches records that \fBn_likes\fP column value is
|
21756
|
-
greater than or equal to \fB10\fP
|
21756
|
+
greater than or equal to \fB10\fP\&.
|
21757
21757
|
.SS Combined expression
|
21758
21758
|
.sp
|
21759
21759
|
Here is available combined expression list.
|
21760
21760
|
.SS Logical OR
|
21761
21761
|
.sp
|
21762
|
-
Its syntax is \fBa OR b\fP
|
21762
|
+
Its syntax is \fBa OR b\fP\&.
|
21763
21763
|
.sp
|
21764
21764
|
\fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
|
21765
21765
|
assignment expressions.
|
@@ -21829,14 +21829,14 @@ greater than \fB10\fP or contain a word \fBsenna\fP in \fBcontent\fP column
|
|
21829
21829
|
value.
|
21830
21830
|
.SS Logical AND
|
21831
21831
|
.sp
|
21832
|
-
Its syntax is \fBa + b\fP or just \fBa b\fP
|
21832
|
+
Its syntax is \fBa + b\fP or just \fBa b\fP\&.
|
21833
21833
|
.sp
|
21834
21834
|
\fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
|
21835
21835
|
assignment expressions.
|
21836
21836
|
.sp
|
21837
21837
|
If both \fBa\fP and \fBb\fP are matched, \fBa + b\fP is matched.
|
21838
21838
|
.sp
|
21839
|
-
You can specify \fB+\fP the first expression such as \fB+a\fP
|
21839
|
+
You can specify \fB+\fP the first expression such as \fB+a\fP\&. The \fB+\fP
|
21840
21840
|
is just ignored.
|
21841
21841
|
.sp
|
21842
21842
|
Here is a simple exmaple.
|
@@ -21896,14 +21896,14 @@ greater than or equal to \fB10\fP and contain a word \fBgroonga\fP in
|
|
21896
21896
|
\fBcontent\fP column value.
|
21897
21897
|
.SS Logical NOT
|
21898
21898
|
.sp
|
21899
|
-
Its syntax is \fBa \- b\fP
|
21899
|
+
Its syntax is \fBa \- b\fP\&.
|
21900
21900
|
.sp
|
21901
21901
|
\fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
|
21902
21902
|
assignment expressions.
|
21903
21903
|
.sp
|
21904
21904
|
If \fBa\fP is matched and \fBb\fP is not matched, \fBa \- b\fP is matched.
|
21905
21905
|
.sp
|
21906
|
-
You can not specify \fB\-\fP the first expression such as \fB\-a\fP
|
21906
|
+
You can not specify \fB\-\fP the first expression such as \fB\-a\fP\&. It\(aqs
|
21907
21907
|
syntax error.
|
21908
21908
|
.sp
|
21909
21909
|
Here is a simple exmaple.
|
@@ -21963,7 +21963,7 @@ greater than or equal to \fB10\fP and don\(aqt contain a word \fBgroonga\fP in
|
|
21963
21963
|
\fBcontent\fP column value.
|
21964
21964
|
.SS Grouping
|
21965
21965
|
.sp
|
21966
|
-
Its syntax is \fB(...)\fP
|
21966
|
+
Its syntax is \fB(...)\fP\&. \fB\&...\fP is space separated expression list.
|
21967
21967
|
.sp
|
21968
21968
|
\fB(...)\fP groups one ore more expressions and they can be
|
21969
21969
|
processed as an expression. \fBa b OR c\fP means that \fBa\fP and \fBb\fP
|
@@ -22091,9 +22091,9 @@ Assignment expression in query syntax has some limitations. So you
|
|
22091
22091
|
should use \fB/reference/grn_expr/script_syntax\fP instead of query syntax for
|
22092
22092
|
assignment.
|
22093
22093
|
.sp
|
22094
|
-
There is only one syntax for assignment expression. It\(aqs \fBcolumn:=value\fP
|
22094
|
+
There is only one syntax for assignment expression. It\(aqs \fBcolumn:=value\fP\&.
|
22095
22095
|
.sp
|
22096
|
-
\fBvalue\fP is assigend to \fBcolumn\fP
|
22096
|
+
\fBvalue\fP is assigend to \fBcolumn\fP\&. \fBvalue\fP is always processed as
|
22097
22097
|
string in query syntax. \fBvalue\fP is casted to the type of \fBcolumn\fP
|
22098
22098
|
automatically. It causes some limitations. For example, you cannot use
|
22099
22099
|
boolean literal such as \fBtrue\fP and \fBfalse\fP for \fBBool\fP type
|
@@ -22105,7 +22105,7 @@ See \fB/reference/cast\fP about cast.
|
|
22105
22105
|
.sp
|
22106
22106
|
Script syntax is a syntax to specify complex search condition. It is
|
22107
22107
|
similar to ECMAScript. For example, \fB_key == "book"\fP means that
|
22108
|
-
groonga searches records that \fB_key\fP value is \fB"book"\fP
|
22108
|
+
groonga searches records that \fB_key\fP value is \fB"book"\fP\&. All values
|
22109
22109
|
are string in \fBquery_syntax\fP but its own type in script
|
22110
22110
|
syntax. For example, \fB"book"\fP is string, \fB1\fP is integer,
|
22111
22111
|
\fBTokenBigram\fP is the object whose name is \fBTokenBigram\fP and so on.
|
@@ -22164,7 +22164,7 @@ load \-\-table Entries
|
|
22164
22164
|
.sp
|
22165
22165
|
There is a table, \fBEntries\fP, for blog entries. An entry has title,
|
22166
22166
|
content and the number of likes for the entry. Title is key of
|
22167
|
-
\fBEntries\fP
|
22167
|
+
\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
|
22168
22168
|
number of likes is value of \fBEntries.n_likes\fP column.
|
22169
22169
|
.sp
|
22170
22170
|
\fBEntries._key\fP column and \fBEntries.content\fP column are indexed
|
@@ -22176,8 +22176,8 @@ OK. The schema and data for examples are ready.
|
|
22176
22176
|
.SS Integer
|
22177
22177
|
.sp
|
22178
22178
|
Integer literal is sequence of \fB0\fP to \fB9\fP such as
|
22179
|
-
\fB1234567890\fP
|
22180
|
-
\fB+29\fP and \fB\-29\fP
|
22179
|
+
\fB1234567890\fP\&. \fB+\fP or \fB\-\fP can be prepended as sign such as
|
22180
|
+
\fB+29\fP and \fB\-29\fP\&. Integer literal must be decimal. Octal notation,
|
22181
22181
|
hex and so on can\(aqt be used.
|
22182
22182
|
.sp
|
22183
22183
|
The maximum value of integer literal is \fB9223372036854775807\fP (\fB= 2
|
@@ -22185,15 +22185,15 @@ The maximum value of integer literal is \fB9223372036854775807\fP (\fB= 2
|
|
22185
22185
|
\fB\-9223372036854775808\fP (\fB= \-(2 ** 63)\fP).
|
22186
22186
|
.SS Float
|
22187
22187
|
.sp
|
22188
|
-
Float literal is sequence of \fB0\fP to \fB9\fP, \fB
|
22189
|
-
such as \fB3.14\fP
|
22190
|
-
\fB+3.14\fP and \fB\-3.14\fP
|
22188
|
+
Float literal is sequence of \fB0\fP to \fB9\fP, \fB\&.\fP and \fB0\fP to \fB9\fP
|
22189
|
+
such as \fB3.14\fP\&. \fB+\fP or \fB\-\fP can be prepended as sign such as
|
22190
|
+
\fB+3.14\fP and \fB\-3.14\fP\&. \fB${RADIX}e${EXPORNENTIAL}\fP and
|
22191
22191
|
\fB${RADIX}E${EXPORNENTIAL}\fP formats are also supported. For example,
|
22192
|
-
\fB314e\-2\fP is the same as \fB3.14\fP
|
22192
|
+
\fB314e\-2\fP is the same as \fB3.14\fP\&.
|
22193
22193
|
.SS String
|
22194
22194
|
.sp
|
22195
|
-
String literal is \fB"..."\fP
|
22196
|
-
prepending \fB\e\e\(aq\(aq such as \(ga\(ga\e"\fP
|
22195
|
+
String literal is \fB"..."\fP\&. You need to escape \fB"\fP in literal by
|
22196
|
+
prepending \fB\e\e\(aq\(aq such as \(ga\(ga\e"\fP\&. For example, \fB"Say \e"Hello!\e"."\fP is
|
22197
22197
|
a literal for \fBSay "Hello!".\fP string.
|
22198
22198
|
.sp
|
22199
22199
|
String encoding must be the same as encoding of database. The default
|
@@ -22202,11 +22202,11 @@ configure option, \fB\-\-encodiong\fP \fB/reference/executables/groonga\fP optio
|
|
22202
22202
|
and so on.
|
22203
22203
|
.SS Boolean
|
22204
22204
|
.sp
|
22205
|
-
Boolean literal is \fBtrue\fP and \fBfalse\fP
|
22205
|
+
Boolean literal is \fBtrue\fP and \fBfalse\fP\&. \fBtrue\fP means true and
|
22206
22206
|
\fBfalse\fP means false.
|
22207
22207
|
.SS Null
|
22208
22208
|
.sp
|
22209
|
-
Null literal is \fBnull\fP
|
22209
|
+
Null literal is \fBnull\fP\&. Groonga doesn\(aqt support null value but null
|
22210
22210
|
literal is supported.
|
22211
22211
|
.SS Time
|
22212
22212
|
.sp
|
@@ -22221,7 +22221,7 @@ Time literal doesn\(aqt exit. There are string time notation, integer
|
|
22221
22221
|
time notation and float time notation.
|
22222
22222
|
.sp
|
22223
22223
|
String time notation is \fB"YYYY/MM/DD hh:mm:ss.uuuuuu"\fP or
|
22224
|
-
\fB"YYYY\-MM\-DD hh:mm:ss.uuuuuu"\fP
|
22224
|
+
\fB"YYYY\-MM\-DD hh:mm:ss.uuuuuu"\fP\&. \fBYYYY\fP is year, \fBMM\fP is month,
|
22225
22225
|
\fBDD\fP is day, \fBhh\fP is hour, \fBmm\fP is minute, \fBss\fP is second and
|
22226
22226
|
\fBuuuuuu\fP is micro second. It is local time. For example,
|
22227
22227
|
\fB"2012/07/23 02:41:10.436218"\fP is \fB2012\-07\-23T02:41:10.436218\fP in
|
@@ -22266,15 +22266,15 @@ String geo point notation has the following patterns:
|
|
22266
22266
|
be represented in milliseconds or degree.
|
22267
22267
|
.SS Array
|
22268
22268
|
.sp
|
22269
|
-
Array literal is \fB[element1, element2, ...]\fP
|
22269
|
+
Array literal is \fB[element1, element2, ...]\fP\&.
|
22270
22270
|
.SS Object literal
|
22271
22271
|
.sp
|
22272
|
-
Object literal is \fB{name1: value1, name2: value2, ...}\fP
|
22272
|
+
Object literal is \fB{name1: value1, name2: value2, ...}\fP\&. Groonga
|
22273
22273
|
doesn\(aqt support object literal yet.
|
22274
22274
|
.SS Control syntaxes
|
22275
22275
|
.sp
|
22276
22276
|
Script syntax doesn\(aqt support statement. So you cannot use control
|
22277
|
-
statement such as \fBif\fP
|
22277
|
+
statement such as \fBif\fP\&. You can only use \fBA ? B : C\fP expression as
|
22278
22278
|
control syntax.
|
22279
22279
|
.sp
|
22280
22280
|
\fBA ? B : C\fP returns \fBB\fP if \fBA\fP is true, \fBC\fP otherwise.
|
@@ -22345,10 +22345,10 @@ select Entries \-\-filter \(aqn_likes == (_id == 1 ? 5 : 3)\(aq
|
|
22345
22345
|
.sp
|
22346
22346
|
The expression matches records that \fB_id\fP column value is equal to \fB1\fP
|
22347
22347
|
and \fBn_likes\fP column value is equal to \fB5\fP or \fB_id\fP column value is
|
22348
|
-
not equal to 1 and \fBn_likes\fP column value is equal to \fB3\fP
|
22348
|
+
not equal to 1 and \fBn_likes\fP column value is equal to \fB3\fP\&.
|
22349
22349
|
.SS Grouping
|
22350
22350
|
.sp
|
22351
|
-
Its syntax is \fB(...)\fP
|
22351
|
+
Its syntax is \fB(...)\fP\&. \fB\&...\fP is comma separated expression list.
|
22352
22352
|
.sp
|
22353
22353
|
\fB(...)\fP groups one ore more expressions and they can be processed as
|
22354
22354
|
an expression. \fBa && b || c\fP means that \fBa\fP and \fBb\fP are matched
|
@@ -22467,10 +22467,10 @@ The second expression uses grouping. It matches records that \fBn_likes
|
|
22467
22467
|
matched.
|
22468
22468
|
.SS Function call
|
22469
22469
|
.sp
|
22470
|
-
Its syntax is \fBname(arugment1, argument2, ...)\fP
|
22470
|
+
Its syntax is \fBname(arugment1, argument2, ...)\fP\&.
|
22471
22471
|
.sp
|
22472
22472
|
\fBname(argument1, argument2, ...)\fP calls a function that is named
|
22473
|
-
\fBname\fP with arguments \fBargument1\fP, \fBargument2\fP and \fB
|
22473
|
+
\fBname\fP with arguments \fBargument1\fP, \fBargument2\fP and \fB\&...\fP\&.
|
22474
22474
|
.sp
|
22475
22475
|
See \fB/reference/function\fP for available functin list.
|
22476
22476
|
.sp
|
@@ -22532,9 +22532,9 @@ select Entries \-\-filter \(aqedit_distance(_key, "Groonga") <= 1\(aq
|
|
22532
22532
|
.UNINDENT
|
22533
22533
|
.UNINDENT
|
22534
22534
|
.sp
|
22535
|
-
The expression uses \fB/reference/functions/edit_distance\fP
|
22535
|
+
The expression uses \fB/reference/functions/edit_distance\fP\&. It
|
22536
22536
|
matches records that \fB_key\fP column value is similar to
|
22537
|
-
\fB"Groonga"\fP
|
22537
|
+
\fB"Groonga"\fP\&. Similality of \fB"Groonga"\fP is computed as edit
|
22538
22538
|
distance. If edit distance is less than or equal to 1, the value is
|
22539
22539
|
treated as similar. In this case, \fB"Groonga"\fP and \fB"Mroonga"\fP are
|
22540
22540
|
treated as similar.
|
@@ -22546,7 +22546,7 @@ Groonga supports operators defined in ECMAScript.
|
|
22546
22546
|
Here are arithmetic operators.
|
22547
22547
|
.SS Addition operator
|
22548
22548
|
.sp
|
22549
|
-
Its syntax is \fBnumber1 + number2\fP
|
22549
|
+
Its syntax is \fBnumber1 + number2\fP\&.
|
22550
22550
|
.sp
|
22551
22551
|
The operator adds \fBnumber1\fP and \fBnumber2\fP and returns the result.
|
22552
22552
|
.sp
|
@@ -22606,7 +22606,7 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
22606
22606
|
to \fB15\fP (= \fB10 + 5\fP).
|
22607
22607
|
.SS Subtraction operator
|
22608
22608
|
.sp
|
22609
|
-
Its syntax is \fBnumber1 \- number2\fP
|
22609
|
+
Its syntax is \fBnumber1 \- number2\fP\&.
|
22610
22610
|
.sp
|
22611
22611
|
The operator subtracts \fBnumber2\fP from \fBnumber1\fP and returns the result.
|
22612
22612
|
.sp
|
@@ -22666,7 +22666,7 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
22666
22666
|
to \fB15\fP (= \fB20 \- 5\fP).
|
22667
22667
|
.SS Multiplication operator
|
22668
22668
|
.sp
|
22669
|
-
Its syntax is \fBnumber1 * number2\fP
|
22669
|
+
Its syntax is \fBnumber1 * number2\fP\&.
|
22670
22670
|
.sp
|
22671
22671
|
The operator multiplies \fBnumber1\fP and \fBnumber2\fP and returns the result.
|
22672
22672
|
.sp
|
@@ -22726,9 +22726,9 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
22726
22726
|
to \fB15\fP (= \fB3 * 5\fP).
|
22727
22727
|
.SS Division operator
|
22728
22728
|
.sp
|
22729
|
-
Its syntax is \fBnumber1 / number2\fP and \fBnumber1 % number2\fP
|
22729
|
+
Its syntax is \fBnumber1 / number2\fP and \fBnumber1 % number2\fP\&.
|
22730
22730
|
.sp
|
22731
|
-
The operator divides \fBnumber2\fP by \fBnumber1\fP
|
22731
|
+
The operator divides \fBnumber2\fP by \fBnumber1\fP\&. \fB/\fP returns the
|
22732
22732
|
quotient of result. \fB%\fP returns the remainder of result.
|
22733
22733
|
.sp
|
22734
22734
|
Here is simple examples.
|
@@ -22849,9 +22849,9 @@ to \fB5\fP (= \fB26 % 7\fP).
|
|
22849
22849
|
Here are logical operators.
|
22850
22850
|
.SS Logical NOT operator
|
22851
22851
|
.sp
|
22852
|
-
Its syntax is \fB!condition\fP
|
22852
|
+
Its syntax is \fB!condition\fP\&.
|
22853
22853
|
.sp
|
22854
|
-
The operator inverts boolean value of \fBcondition\fP
|
22854
|
+
The operator inverts boolean value of \fBcondition\fP\&.
|
22855
22855
|
.sp
|
22856
22856
|
Here is a simple example.
|
22857
22857
|
.sp
|
@@ -22924,10 +22924,10 @@ select Entries \-\-filter \(aq!(n_likes == 5)\(aq
|
|
22924
22924
|
.UNINDENT
|
22925
22925
|
.sp
|
22926
22926
|
The expression matches records that \fBn_likes\fP column value is not
|
22927
|
-
equal to \fB5\fP
|
22927
|
+
equal to \fB5\fP\&.
|
22928
22928
|
.SS Logical AND operator
|
22929
22929
|
.sp
|
22930
|
-
Its syntax is \fBcondition1 && condition2\fP
|
22930
|
+
Its syntax is \fBcondition1 && condition2\fP\&.
|
22931
22931
|
.sp
|
22932
22932
|
The operator returns true if both of \fBcondition1\fP and
|
22933
22933
|
\fBcondition2\fP are true, false otherwise.
|
@@ -22992,10 +22992,10 @@ select Entries \-\-filter \(aqcontent @ "fast" && n_likes >= 10\(aq
|
|
22992
22992
|
.sp
|
22993
22993
|
The expression matches records that \fBcontent\fP column value has the
|
22994
22994
|
word \fBfast\fP and \fBn_likes\fP column value is greater or equal to
|
22995
|
-
\fB10\fP
|
22995
|
+
\fB10\fP\&.
|
22996
22996
|
.SS Logical OR operator
|
22997
22997
|
.sp
|
22998
|
-
Its syntax is \fBcondition1 || condition2\fP
|
22998
|
+
Its syntax is \fBcondition1 || condition2\fP\&.
|
22999
22999
|
.sp
|
23000
23000
|
The operator returns true if either \fBcondition1\fP or \fBcondition2\fP is
|
23001
23001
|
true, false otherwise.
|
@@ -23059,10 +23059,10 @@ select Entries \-\-filter \(aqn_likes == 5 || n_likes == 10\(aq
|
|
23059
23059
|
.UNINDENT
|
23060
23060
|
.sp
|
23061
23061
|
The expression matches records that \fBn_likes\fP column value is equal
|
23062
|
-
to \fB5\fP or \fB10\fP
|
23062
|
+
to \fB5\fP or \fB10\fP\&.
|
23063
23063
|
.SS Logical AND NOT operator
|
23064
23064
|
.sp
|
23065
|
-
Its syntax is \fBcondition1 &! condition2\fP
|
23065
|
+
Its syntax is \fBcondition1 &! condition2\fP\&.
|
23066
23066
|
.sp
|
23067
23067
|
The operator returns true if \fBcondition1\fP is true but \fBcondition2\fP
|
23068
23068
|
is false, false otherwise. It returns difference set.
|
@@ -23120,15 +23120,15 @@ select Entries \-\-filter \(aqcontent @ "fast" &! content @ "mroonga"\(aq
|
|
23120
23120
|
.UNINDENT
|
23121
23121
|
.sp
|
23122
23122
|
The expression matches records that \fBcontent\fP column value has the
|
23123
|
-
word \fBfast\fP but doesn\(aqt have the word \fBmroonga\fP
|
23123
|
+
word \fBfast\fP but doesn\(aqt have the word \fBmroonga\fP\&.
|
23124
23124
|
.SS Bitwise operators
|
23125
23125
|
.sp
|
23126
23126
|
Here are bitwise operators.
|
23127
23127
|
.SS Bitwise NOT operator
|
23128
23128
|
.sp
|
23129
|
-
Its syntax is \fB~number\fP
|
23129
|
+
Its syntax is \fB~number\fP\&.
|
23130
23130
|
.sp
|
23131
|
-
The operator returns bitwise NOT of \fBnumber\fP
|
23131
|
+
The operator returns bitwise NOT of \fBnumber\fP\&.
|
23132
23132
|
.sp
|
23133
23133
|
Here is a simple example.
|
23134
23134
|
.sp
|
@@ -23183,12 +23183,12 @@ select Entries \-\-filter \(aq~n_likes == \-6\(aq
|
|
23183
23183
|
.UNINDENT
|
23184
23184
|
.sp
|
23185
23185
|
The expression matches records that \fBn_likes\fP column value is equal
|
23186
|
-
to \fB5\fP because bitwise NOT of \fB5\fP is equal to \fB\-6\fP
|
23186
|
+
to \fB5\fP because bitwise NOT of \fB5\fP is equal to \fB\-6\fP\&.
|
23187
23187
|
.SS Bitwise AND operator
|
23188
23188
|
.sp
|
23189
|
-
Its syntax is \fBnumber1 & number2\fP
|
23189
|
+
Its syntax is \fBnumber1 & number2\fP\&.
|
23190
23190
|
.sp
|
23191
|
-
The operator returns bitwise AND between \fBnumber1\fP and \fBnumber2\fP
|
23191
|
+
The operator returns bitwise AND between \fBnumber1\fP and \fBnumber2\fP\&.
|
23192
23192
|
.sp
|
23193
23193
|
Here is a simple example.
|
23194
23194
|
.sp
|
@@ -23263,12 +23263,12 @@ select Entries \-\-filter \(aq(n_likes & 1) == 1\(aq
|
|
23263
23263
|
The expression matches records that \fBn_likes\fP column value is even
|
23264
23264
|
number because bitwise AND between an even number and \fB1\fP is equal
|
23265
23265
|
to \fB1\fP and bitwise AND between an odd number and \fB1\fP is equal to
|
23266
|
-
\fB0\fP
|
23266
|
+
\fB0\fP\&.
|
23267
23267
|
.SS Bitwise OR operator
|
23268
23268
|
.sp
|
23269
|
-
Its syntax is \fBnumber1 | number2\fP
|
23269
|
+
Its syntax is \fBnumber1 | number2\fP\&.
|
23270
23270
|
.sp
|
23271
|
-
The operator returns bitwise OR between \fBnumber1\fP and \fBnumber2\fP
|
23271
|
+
The operator returns bitwise OR between \fBnumber1\fP and \fBnumber2\fP\&.
|
23272
23272
|
.sp
|
23273
23273
|
Here is a simple example.
|
23274
23274
|
.sp
|
@@ -23326,9 +23326,9 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
23326
23326
|
to \fB5\fP (= \fB1 | 4\fP).
|
23327
23327
|
.SS Bitwise XOR operator
|
23328
23328
|
.sp
|
23329
|
-
Its syntax is \fBnumber1 ^ number2\fP
|
23329
|
+
Its syntax is \fBnumber1 ^ number2\fP\&.
|
23330
23330
|
.sp
|
23331
|
-
The operator returns bitwise XOR between \fBnumber1\fP and \fBnumber2\fP
|
23331
|
+
The operator returns bitwise XOR between \fBnumber1\fP and \fBnumber2\fP\&.
|
23332
23332
|
.sp
|
23333
23333
|
Here is a simple example.
|
23334
23334
|
.sp
|
@@ -23389,10 +23389,10 @@ to \fB5\fP (= \fB10 ^ 15\fP).
|
|
23389
23389
|
Here are shift operators.
|
23390
23390
|
.SS Left shift operator
|
23391
23391
|
.sp
|
23392
|
-
Its syntax is \fBnumber1 << number2\fP
|
23392
|
+
Its syntax is \fBnumber1 << number2\fP\&.
|
23393
23393
|
.sp
|
23394
23394
|
The operator performs a bitwise left shift operation on \fBnumber1\fP by
|
23395
|
-
\fBnumber2\fP
|
23395
|
+
\fBnumber2\fP\&.
|
23396
23396
|
.sp
|
23397
23397
|
Here is a simple example.
|
23398
23398
|
.sp
|
@@ -23450,10 +23450,10 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
23450
23450
|
to \fB10\fP (= \fB5 << 1\fP).
|
23451
23451
|
.SS Signed right shift operator
|
23452
23452
|
.sp
|
23453
|
-
Its syntax is \fBnumber1 >> number2\fP
|
23453
|
+
Its syntax is \fBnumber1 >> number2\fP\&.
|
23454
23454
|
.sp
|
23455
|
-
The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP
|
23456
|
-
of the result is the same as \fBnumber1\fP
|
23455
|
+
The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP\&. The sign
|
23456
|
+
of the result is the same as \fBnumber1\fP\&.
|
23457
23457
|
.sp
|
23458
23458
|
Here is a simple example.
|
23459
23459
|
.sp
|
@@ -23511,10 +23511,10 @@ The expression matches records that \fBn_likes\fP column value is equal
|
|
23511
23511
|
to \fB5\fP (= \fB\-(\-10 >> 1)\fP = \fB\-(\-5)\fP).
|
23512
23512
|
.SS Unsigned right shift operator
|
23513
23513
|
.sp
|
23514
|
-
Its syntax is \fBnumber1 >>> number2\fP
|
23514
|
+
Its syntax is \fBnumber1 >>> number2\fP\&.
|
23515
23515
|
.sp
|
23516
|
-
The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP
|
23517
|
-
leftmost \fBnumber2\fP bits are filled by \fB0\fP
|
23516
|
+
The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP\&. The
|
23517
|
+
leftmost \fBnumber2\fP bits are filled by \fB0\fP\&.
|
23518
23518
|
.sp
|
23519
23519
|
Here is a simple example.
|
23520
23520
|
.sp
|
@@ -23575,7 +23575,7 @@ to \fB5\fP (= \fB2147483648 \- (\-10 >>> 1)\fP = \fB2147483648 \- 2147483643\fP)
|
|
23575
23575
|
Here are comparison operators.
|
23576
23576
|
.SS Equal operator
|
23577
23577
|
.sp
|
23578
|
-
Its syntax is \fBobject1 == object2\fP
|
23578
|
+
Its syntax is \fBobject1 == object2\fP\&.
|
23579
23579
|
.sp
|
23580
23580
|
The operator returns true if \fBobject1\fP equals to \fBobject2\fP, false
|
23581
23581
|
otherwise.
|
@@ -23633,10 +23633,10 @@ select Entries \-\-filter \(aqn_likes == 5\(aq
|
|
23633
23633
|
.UNINDENT
|
23634
23634
|
.sp
|
23635
23635
|
The expression matches records that \fBn_likes\fP column value is equal
|
23636
|
-
to \fB5\fP
|
23636
|
+
to \fB5\fP\&.
|
23637
23637
|
.SS Not equal operator
|
23638
23638
|
.sp
|
23639
|
-
Its syntax is \fBobject1 != object2\fP
|
23639
|
+
Its syntax is \fBobject1 != object2\fP\&.
|
23640
23640
|
.sp
|
23641
23641
|
The operator returns true if \fBobject1\fP does not equal to
|
23642
23642
|
\fBobject2\fP, false otherwise.
|
@@ -23712,7 +23712,7 @@ select Entries \-\-filter \(aqn_likes != 5\(aq
|
|
23712
23712
|
.UNINDENT
|
23713
23713
|
.sp
|
23714
23714
|
The expression matches records that \fBn_likes\fP column value is not
|
23715
|
-
equal to \fB5\fP
|
23715
|
+
equal to \fB5\fP\&.
|
23716
23716
|
.SS Less than operator
|
23717
23717
|
.sp
|
23718
23718
|
TODO: ...
|
@@ -23728,7 +23728,7 @@ TODO: ...
|
|
23728
23728
|
.SS Assignment operators
|
23729
23729
|
.SS Addition assignment operator
|
23730
23730
|
.sp
|
23731
|
-
Its syntax is \fBcolumn1 += column2\fP
|
23731
|
+
Its syntax is \fBcolumn1 += column2\fP\&.
|
23732
23732
|
.sp
|
23733
23733
|
The operator performs addition assginment operation on column1 by column2.
|
23734
23734
|
.sp
|
@@ -23806,7 +23806,7 @@ is 3.
|
|
23806
23806
|
So the expression \fB1 + 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
23807
23807
|
.SS Subtraction assignment operator
|
23808
23808
|
.sp
|
23809
|
-
Its syntax is \fBcolumn1 \-= column2\fP
|
23809
|
+
Its syntax is \fBcolumn1 \-= column2\fP\&.
|
23810
23810
|
.sp
|
23811
23811
|
The operator performs subtraction assginment operation on column1 by column2.
|
23812
23812
|
.sp
|
@@ -23884,7 +23884,7 @@ is 3.
|
|
23884
23884
|
So the expression \fB1 \- 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
23885
23885
|
.SS Multiplication assignment operator
|
23886
23886
|
.sp
|
23887
|
-
Its syntax is \fBcolumn1 *= column2\fP
|
23887
|
+
Its syntax is \fBcolumn1 *= column2\fP\&.
|
23888
23888
|
.sp
|
23889
23889
|
The operator performs multiplication assginment operation on column1 by column2.
|
23890
23890
|
.sp
|
@@ -23962,7 +23962,7 @@ is 3.
|
|
23962
23962
|
So the expression \fB1 * 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
23963
23963
|
.SS Division assignment operator
|
23964
23964
|
.sp
|
23965
|
-
Its syntax is \fBcolumn1 /= column2\fP
|
23965
|
+
Its syntax is \fBcolumn1 /= column2\fP\&.
|
23966
23966
|
.sp
|
23967
23967
|
The operator performs division assginment operation on column1 by column2.
|
23968
23968
|
.sp
|
@@ -24040,7 +24040,7 @@ is 3.
|
|
24040
24040
|
So the expression \fB1 / 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
24041
24041
|
.SS Modulo assignment operator
|
24042
24042
|
.sp
|
24043
|
-
Its syntax is \fBcolumn1 %= column2\fP
|
24043
|
+
Its syntax is \fBcolumn1 %= column2\fP\&.
|
24044
24044
|
.sp
|
24045
24045
|
The operator performs modulo assginment operation on column1 by column2.
|
24046
24046
|
.sp
|
@@ -24118,7 +24118,7 @@ is 3.
|
|
24118
24118
|
So the expression \fB1 % 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
24119
24119
|
.SS Bitwise left shift assignment operator
|
24120
24120
|
.sp
|
24121
|
-
Its syntax is \fBcolumn1 <<= column2\fP
|
24121
|
+
Its syntax is \fBcolumn1 <<= column2\fP\&.
|
24122
24122
|
.sp
|
24123
24123
|
The operator performs left shift assginment operation on column1 by column2.
|
24124
24124
|
.sp
|
@@ -24196,17 +24196,17 @@ is 3.
|
|
24196
24196
|
So the expression \fB1 << 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
24197
24197
|
.SS Bitwise signed right shift assignment operator
|
24198
24198
|
.sp
|
24199
|
-
Its syntax is \fBcolumn2 >>= column2\fP
|
24199
|
+
Its syntax is \fBcolumn2 >>= column2\fP\&.
|
24200
24200
|
.sp
|
24201
24201
|
The operator performs signed right shift assginment operation on column1 by column2.
|
24202
24202
|
.SS Bitwise unsigned right shift assignment operator
|
24203
24203
|
.sp
|
24204
|
-
Its syntax is \fBcolumn1 >>>= column2\fP
|
24204
|
+
Its syntax is \fBcolumn1 >>>= column2\fP\&.
|
24205
24205
|
.sp
|
24206
24206
|
The operator performs unsigned right shift assginment operation on column1 by column2.
|
24207
24207
|
.SS Bitwise AND assignment operator
|
24208
24208
|
.sp
|
24209
|
-
Its syntax is \fBcolumn1 &= column2\fP
|
24209
|
+
Its syntax is \fBcolumn1 &= column2\fP\&.
|
24210
24210
|
.sp
|
24211
24211
|
The operator performs bitwise AND assignment operation on column1 by column2.
|
24212
24212
|
.sp
|
@@ -24284,7 +24284,7 @@ is 10.
|
|
24284
24284
|
So the expression \fB1 & 10\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
24285
24285
|
.SS Bitwise OR assignment operator
|
24286
24286
|
.sp
|
24287
|
-
Its syntax is \fBcolumn1 |= column2\fP
|
24287
|
+
Its syntax is \fBcolumn1 |= column2\fP\&.
|
24288
24288
|
.sp
|
24289
24289
|
The operator performs bitwise OR assignment operation on column1 by column2.
|
24290
24290
|
.sp
|
@@ -24362,7 +24362,7 @@ is 10.
|
|
24362
24362
|
So the expression \fB1 | 10\fP is evaluated and stored to \fB_score\fP column as the execution result.
|
24363
24363
|
.SS Bitwise XOR assignment operator
|
24364
24364
|
.sp
|
24365
|
-
Its syntax is \fBcolumn1 ^= column2\fP
|
24365
|
+
Its syntax is \fBcolumn1 ^= column2\fP\&.
|
24366
24366
|
.sp
|
24367
24367
|
The operator performs bitwise XOR assginment operation on column1 by column2.
|
24368
24368
|
.sp
|
@@ -24442,12 +24442,12 @@ So the expression \fB1 ^ 3\fP is evaluated and stored to \fB_score\fP column as
|
|
24442
24442
|
.sp
|
24443
24443
|
Script syntax adds the original binary opearators to ECMAScript
|
24444
24444
|
syntax. They operate search specific operations. They are starts with
|
24445
|
-
\fB@\fP or \fB*\fP
|
24445
|
+
\fB@\fP or \fB*\fP\&.
|
24446
24446
|
.SS Match operator
|
24447
24447
|
.sp
|
24448
|
-
Its syntax is \fBcolumn @ value\fP
|
24448
|
+
Its syntax is \fBcolumn @ value\fP\&.
|
24449
24449
|
.sp
|
24450
|
-
The operator searches \fBvalue\fP by inverted index of \fBcolumn\fP
|
24450
|
+
The operator searches \fBvalue\fP by inverted index of \fBcolumn\fP\&.
|
24451
24451
|
Normally, full text search is operated but tag search can be operated.
|
24452
24452
|
Because tag search is also implemented by inverted index.
|
24453
24453
|
.sp
|
@@ -24497,17 +24497,17 @@ The expression matches records that contain a word \fBfast\fP in
|
|
24497
24497
|
\fBcontent\fP column value.
|
24498
24498
|
.SS Prefix search operator
|
24499
24499
|
.sp
|
24500
|
-
Its syntax is \fBcolumn @^ value\fP
|
24500
|
+
Its syntax is \fBcolumn @^ value\fP\&.
|
24501
24501
|
.sp
|
24502
|
-
The operator does prefix search with \fBvalue\fP
|
24503
|
-
records that contain a word that starts with \fBvalue\fP
|
24502
|
+
The operator does prefix search with \fBvalue\fP\&. Prefix search searches
|
24503
|
+
records that contain a word that starts with \fBvalue\fP\&.
|
24504
24504
|
.sp
|
24505
24505
|
You can use fast prefix search against a column. The column must be
|
24506
24506
|
indexed and index table must be patricia trie table
|
24507
24507
|
(\fBTABLE_PAT_KEY\fP) or double array trie table
|
24508
24508
|
(\fBTABLE_DAT_KEY\fP). You can also use fast prefix search against
|
24509
24509
|
\fB_key\fP pseudo column of patricia trie table or double array trie
|
24510
|
-
table. You don\(aqt need to index \fB_key\fP
|
24510
|
+
table. You don\(aqt need to index \fB_key\fP\&.
|
24511
24511
|
.sp
|
24512
24512
|
Prefix search can be used with other table types but it causes all
|
24513
24513
|
records scan. It\(aqs not problem for small records but it spends more
|
@@ -24558,17 +24558,17 @@ The expression matches records that contain a word that starts with
|
|
24558
24558
|
\fBGood\-bye Tritonn\fP are matched with the expression.
|
24559
24559
|
.SS Suffix search operator
|
24560
24560
|
.sp
|
24561
|
-
Its syntax is \fBcolumn @$ value\fP
|
24561
|
+
Its syntax is \fBcolumn @$ value\fP\&.
|
24562
24562
|
.sp
|
24563
|
-
This operator does suffix search with \fBvalue\fP
|
24564
|
-
searches records that contain a word that ends with \fBvalue\fP
|
24563
|
+
This operator does suffix search with \fBvalue\fP\&. Suffix search
|
24564
|
+
searches records that contain a word that ends with \fBvalue\fP\&.
|
24565
24565
|
.sp
|
24566
24566
|
You can use fast suffix search against a column. The column must be
|
24567
24567
|
indexed and index table must be patricia trie table
|
24568
24568
|
(\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You can also use fast
|
24569
24569
|
suffix search against \fB_key\fP pseudo column of patricia trie table
|
24570
24570
|
(\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You don\(aqt need to
|
24571
|
-
index \fB_key\fP
|
24571
|
+
index \fB_key\fP\&. We recommended that you use index column based fast
|
24572
24572
|
suffix search instead of \fB_key\fP based fast suffix search. \fB_key\fP
|
24573
24573
|
based fast suffix search returns automatically registered
|
24574
24574
|
substrings. (TODO: write document about suffix search and link to it
|
@@ -24656,9 +24656,9 @@ in \fBcontent\fP column value. \fBぐるんが\fP and \fBむるんが\fP are mat
|
|
24656
24656
|
with the expression.
|
24657
24657
|
.SS Near search operator
|
24658
24658
|
.sp
|
24659
|
-
Its syntax is \fBcolumn *N "word1 word2 ..."\fP
|
24659
|
+
Its syntax is \fBcolumn *N "word1 word2 ..."\fP\&.
|
24660
24660
|
.sp
|
24661
|
-
The operator does near search with words \fBword1 word2 ...\fP
|
24661
|
+
The operator does near search with words \fBword1 word2 ...\fP\&. Near
|
24662
24662
|
search searches records that contain the words and the words are
|
24663
24663
|
appeared in the near distance. Near distance is always \fB10\fP for
|
24664
24664
|
now. The unit of near distance is the number of characters in N\-gram
|
@@ -24671,7 +24671,7 @@ only word into tokens. So the unit for ASCII words with
|
|
24671
24671
|
N\-gram family tokenizer.)
|
24672
24672
|
.sp
|
24673
24673
|
Note that an index column for full text search must be defined for
|
24674
|
-
\fBcolumn\fP
|
24674
|
+
\fBcolumn\fP\&.
|
24675
24675
|
.sp
|
24676
24676
|
Here is a simple exmaple.
|
24677
24677
|
.sp
|
@@ -24755,14 +24755,14 @@ also very fast! Really fast!\fP is matched. The number of words between
|
|
24755
24755
|
\fBalso\fP and \fBReally\fP is 10.
|
24756
24756
|
.SS Similar search
|
24757
24757
|
.sp
|
24758
|
-
Its syntax is \fBcolumn *S "document"\fP
|
24758
|
+
Its syntax is \fBcolumn *S "document"\fP\&.
|
24759
24759
|
.sp
|
24760
|
-
The operator does similar search with document \fBdocument\fP
|
24760
|
+
The operator does similar search with document \fBdocument\fP\&. Similar
|
24761
24761
|
search searches records that have similar content to
|
24762
|
-
\fBdocument\fP
|
24762
|
+
\fBdocument\fP\&.
|
24763
24763
|
.sp
|
24764
24764
|
Note that an index column for full text search must be defined for
|
24765
|
-
\fBcolumn\fP
|
24765
|
+
\fBcolumn\fP\&.
|
24766
24766
|
.sp
|
24767
24767
|
Here is a simple exmaple.
|
24768
24768
|
.sp
|
@@ -24805,14 +24805,14 @@ select Entries \-\-filter \(aqcontent *S "I migrated all Solr system!"\(aq \-\-o
|
|
24805
24805
|
.UNINDENT
|
24806
24806
|
.sp
|
24807
24807
|
The expression matches records that have similar content to \fBI
|
24808
|
-
migrated all Solr system!\fP
|
24808
|
+
migrated all Solr system!\fP\&. In this case, records that have \fBI
|
24809
24809
|
migrated all XXX system!\fP content are matched.
|
24810
24810
|
.SS Term extract operator
|
24811
24811
|
.sp
|
24812
|
-
Its syntax is \fB_key *T "document"\fP
|
24812
|
+
Its syntax is \fB_key *T "document"\fP\&.
|
24813
24813
|
.sp
|
24814
|
-
The operator extracts terms from \fBdocument\fP
|
24815
|
-
registered as keys of the table of \fB_key\fP
|
24814
|
+
The operator extracts terms from \fBdocument\fP\&. Terms must be
|
24815
|
+
registered as keys of the table of \fB_key\fP\&.
|
24816
24816
|
.sp
|
24817
24817
|
Note that the table must be patricia trie (\fBTABLE_PAT_KEY\fP) or
|
24818
24818
|
double array trie (\fBTABLE_DAT_KEY\fP). You can\(aqt use hash table
|
@@ -24871,9 +24871,9 @@ select Words \-\-filter \(aq_key *T "Groonga is the successor project to Senna."
|
|
24871
24871
|
.UNINDENT
|
24872
24872
|
.sp
|
24873
24873
|
The expression extrcts terms that included in document \fBGroonga is
|
24874
|
-
the successor project to Senna.\fP
|
24875
|
-
flag is specified to \fBWords\fP
|
24876
|
-
if it is loaded as \fBgroonga\fP into \fBWords\fP
|
24874
|
+
the successor project to Senna.\fP\&. In this case, \fBKEY_NORMALIZE\fP
|
24875
|
+
flag is specified to \fBWords\fP\&. So \fBGroonga\fP can be extracted even
|
24876
|
+
if it is loaded as \fBgroonga\fP into \fBWords\fP\&. All of extracted terms
|
24877
24877
|
are also normalized.
|
24878
24878
|
.SS See also
|
24879
24879
|
.INDENT 0.0
|
@@ -24888,7 +24888,7 @@ are also normalized.
|
|
24888
24888
|
.sp
|
24889
24889
|
Function can be used in some commands. For example, you can use
|
24890
24890
|
function in \fB\-\-filter\fP, \fB\-\-scorer\fP and \fBoutput_columns\fP
|
24891
|
-
options of \fBcommands/select\fP
|
24891
|
+
options of \fBcommands/select\fP\&.
|
24892
24892
|
.sp
|
24893
24893
|
This section describes about function and built\-in functions.
|
24894
24894
|
.sp
|
@@ -24897,7 +24897,7 @@ TODO: Add documentations about function.
|
|
24897
24897
|
.SS Summary
|
24898
24898
|
.sp
|
24899
24899
|
\fBbetween\fP is used for checking the specified value exists in the specific range.
|
24900
|
-
It is often used for combination with \fIselect\-filter\fP option in \fB/reference/commands/select\fP
|
24900
|
+
It is often used for combination with \fIselect\-filter\fP option in \fB/reference/commands/select\fP\&.
|
24901
24901
|
.SS Syntax
|
24902
24902
|
.sp
|
24903
24903
|
\fBbetween\fP has five parameters:
|
@@ -25076,7 +25076,7 @@ In the above case, it returns all the records, because 14 exists in between 13 a
|
|
25076
25076
|
This behavior is used for checking the specified value exists or not in the table.
|
25077
25077
|
.SS Parameters
|
25078
25078
|
.sp
|
25079
|
-
There are five required parameters, \fBcolumn_or_value\fP, and \fBmin\fP, \fBmin_border\fP, \fBmax\fP and \fBmax_border\fP
|
25079
|
+
There are five required parameters, \fBcolumn_or_value\fP, and \fBmin\fP, \fBmin_border\fP, \fBmax\fP and \fBmax_border\fP\&.
|
25080
25080
|
.SS \fBcolumn_or_value\fP
|
25081
25081
|
.sp
|
25082
25082
|
It specifies a column of the table or the value.
|
@@ -25116,7 +25116,7 @@ edit_distance(string1, string2)
|
|
25116
25116
|
.UNINDENT
|
25117
25117
|
.SS 説明
|
25118
25118
|
.sp
|
25119
|
-
|
25119
|
+
Groonga組込関数の一つであるedit_distanceについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
|
25120
25120
|
.sp
|
25121
25121
|
edit_distance() 関数は、string1に指定した文字列とstring2に指定した文字列の間の編集距離を求めます。
|
25122
25122
|
.SS 引数
|
@@ -25169,27 +25169,27 @@ geo_distance(point1, point2, approximate_type)
|
|
25169
25169
|
.UNINDENT
|
25170
25170
|
.UNINDENT
|
25171
25171
|
.sp
|
25172
|
-
The default value of \fBapproximate_type\fP is \fB"rectangle"\fP
|
25172
|
+
The default value of \fBapproximate_type\fP is \fB"rectangle"\fP\&.
|
25173
25173
|
If you omit \fBapproximate_type\fP, \fBgeo_distance\fP calculates the value of
|
25174
25174
|
distance as if \fB"rectangle"\fP was specified.
|
25175
25175
|
.SS Usage
|
25176
25176
|
.sp
|
25177
|
-
\fBgeo_distance\fP is one of the
|
25177
|
+
\fBgeo_distance\fP is one of the Groonga builtin functions.
|
25178
25178
|
.sp
|
25179
25179
|
You can call a builtin function in \fB/reference/grn_expr\fP
|
25180
25180
|
.sp
|
25181
25181
|
\fBgeo_distance\fP function calculates the value of distance (approximate value)
|
25182
|
-
between the coordinate of \fBpoint1\fP and the coordinate of \fBpoint2\fP
|
25182
|
+
between the coordinate of \fBpoint1\fP and the coordinate of \fBpoint2\fP\&.
|
25183
25183
|
.sp
|
25184
25184
|
\fBNOTE:\fP
|
25185
25185
|
.INDENT 0.0
|
25186
25186
|
.INDENT 3.5
|
25187
|
-
|
25188
|
-
There are \fBgeo_distance()\fP, \fBgeo_distance2()\fP and \fBgeo_distance3()\fP
|
25187
|
+
Groonga provides three built in functions for calculating the value of distance.
|
25188
|
+
There are \fBgeo_distance()\fP, \fBgeo_distance2()\fP and \fBgeo_distance3()\fP\&.
|
25189
25189
|
The difference of them is the algorithm of calculating distance.
|
25190
25190
|
\fBgeo_distance2()\fP and \fBgeo_distance3()\fP were deprecated since version 1.2.9.
|
25191
|
-
Use \fBgeo_distance(point1, point2, "sphere")\fP instead of \fBgeo_distance2(point1, point2)\fP
|
25192
|
-
Use \fBgeo_distance(point1, point2, "ellipsoid")\fP instead of \fBgeo_distance3(point1, point2)\fP
|
25191
|
+
Use \fBgeo_distance(point1, point2, "sphere")\fP instead of \fBgeo_distance2(point1, point2)\fP\&.
|
25192
|
+
Use \fBgeo_distance(point1, point2, "ellipsoid")\fP instead of \fBgeo_distance3(point1, point2)\fP\&.
|
25193
25193
|
.UNINDENT
|
25194
25194
|
.UNINDENT
|
25195
25195
|
.sp
|
@@ -25253,7 +25253,7 @@ load \-\-table Cities
|
|
25253
25253
|
.UNINDENT
|
25254
25254
|
.UNINDENT
|
25255
25255
|
.sp
|
25256
|
-
This execution example creates a table named \fBCities\fP which has one column named \fBlocation\fP
|
25256
|
+
This execution example creates a table named \fBCities\fP which has one column named \fBlocation\fP\&.
|
25257
25257
|
\fBlocation\fP column stores the value of coordinate.
|
25258
25258
|
The coordinate of Tokyo is stored as sample data.
|
25259
25259
|
.sp
|
@@ -25340,7 +25340,7 @@ load \-\-table Geo
|
|
25340
25340
|
.UNINDENT
|
25341
25341
|
.UNINDENT
|
25342
25342
|
.sp
|
25343
|
-
This execution example creates a table named \fBGeo\fP which has one column named \fBdistance\fP
|
25343
|
+
This execution example creates a table named \fBGeo\fP which has one column named \fBdistance\fP\&.
|
25344
25344
|
\fBdistance\fP column stores the value of distance.
|
25345
25345
|
.sp
|
25346
25346
|
Execution example:
|
@@ -25383,7 +25383,7 @@ and the coordinate of New York to calculate distance.
|
|
25383
25383
|
.SS Parameters
|
25384
25384
|
.SS Required parameter
|
25385
25385
|
.sp
|
25386
|
-
There are two required parameter, \fBpoint1\fP and \fBpoint2\fP
|
25386
|
+
There are two required parameter, \fBpoint1\fP and \fBpoint2\fP\&.
|
25387
25387
|
.SS \fBpoint1\fP
|
25388
25388
|
.sp
|
25389
25389
|
It specifies the start point that
|
@@ -25403,7 +25403,7 @@ the string indicating the coordinate.
|
|
25403
25403
|
See \fB/reference/types\fP about GeoPoint and the coordinate.
|
25404
25404
|
.SS Optional parameter
|
25405
25405
|
.sp
|
25406
|
-
There is a optional parameter, \fBapproximate_type\fP
|
25406
|
+
There is a optional parameter, \fBapproximate_type\fP\&.
|
25407
25407
|
.SS \fBapproximate_type\fP
|
25408
25408
|
.sp
|
25409
25409
|
It specifies how to approximate the geographical features for calculating
|
@@ -25426,11 +25426,11 @@ You can specify the value of \fBapproximate_type\fP by one of the followings.
|
|
25426
25426
|
\fBNOTE:\fP
|
25427
25427
|
.INDENT 0.0
|
25428
25428
|
.INDENT 3.5
|
25429
|
-
There is a limitation about \fBgeo_distance\fP
|
25429
|
+
There is a limitation about \fBgeo_distance\fP\&. \fBgeo_distance\fP can not
|
25430
25430
|
calculate the value of distance between two points across meridian,
|
25431
25431
|
equator or the date line if you use \fBsphere\fP or \fBellipsoid\fP as
|
25432
|
-
approximate type. There is not such a limitation for \fBrectangle\fP
|
25433
|
-
This is temporary limitation according to the implementation of
|
25432
|
+
approximate type. There is not such a limitation for \fBrectangle\fP\&.
|
25433
|
+
This is temporary limitation according to the implementation of Groonga,
|
25434
25434
|
but it will be fixed in the future release.
|
25435
25435
|
.UNINDENT
|
25436
25436
|
.UNINDENT
|
@@ -25647,7 +25647,7 @@ The return value of \fBgeo_distance("143660000x419009000", "135960000x\-44076000
|
|
25647
25647
|
.INDENT 3.5
|
25648
25648
|
\fBgeo_distance\fP accepts the string indicating the coordinate as
|
25649
25649
|
the value of \fBpoint1\fP when the value of \fBapproximate_type\fP is
|
25650
|
-
\fB"rectangle"\fP
|
25650
|
+
\fB"rectangle"\fP\&.
|
25651
25651
|
If you specified the string indicating the coordinate as the value
|
25652
25652
|
of \fBpoint1\fP with \fBsphere\fP or \fBellipsoid\fP, \fBgeo_distance\fP
|
25653
25653
|
returns 0 as the value of distance.
|
@@ -25659,7 +25659,7 @@ This parameter require to approximate the geographical features
|
|
25659
25659
|
by spherical approximation for calculating the distance.
|
25660
25660
|
.sp
|
25661
25661
|
It is slower than \fBrectangle\fP, but the error of distance becomes
|
25662
|
-
smaller than \fBrectangle\fP
|
25662
|
+
smaller than \fBrectangle\fP\&.
|
25663
25663
|
.sp
|
25664
25664
|
You can also specify \fBsphr\fP as abbrev expression.
|
25665
25665
|
.sp
|
@@ -25706,7 +25706,7 @@ by ellipsoid approximation for calculating the distance.
|
|
25706
25706
|
.sp
|
25707
25707
|
It uses the calculation of distance by the formula of Hubeny.
|
25708
25708
|
It is slower than \fBsphere\fP, but the error of distance becomes
|
25709
|
-
smaller than \fBsphere\fP
|
25709
|
+
smaller than \fBsphere\fP\&.
|
25710
25710
|
.sp
|
25711
25711
|
You can also specify \fBellip\fP as abbrev expression.
|
25712
25712
|
.sp
|
@@ -25770,7 +25770,7 @@ geo_in_circle(point, center, radious_or_point[, approximate_type])
|
|
25770
25770
|
.UNINDENT
|
25771
25771
|
.SS 説明
|
25772
25772
|
.sp
|
25773
|
-
|
25773
|
+
Groonga組込関数の一つであるgeo_in_circleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
|
25774
25774
|
.sp
|
25775
25775
|
geo_in_circle() 関数は、pointに指定した座標が、centerに指定した座標を中心とする円の範囲内にあるかどうかを調べます。
|
25776
25776
|
.SS 引数
|
@@ -25867,7 +25867,7 @@ geo_in_rectangle(point, top_left, bottom_right)
|
|
25867
25867
|
.UNINDENT
|
25868
25868
|
.SS 説明
|
25869
25869
|
.sp
|
25870
|
-
|
25870
|
+
Groonga組込関数の一つであるgeo_in_rectangleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
|
25871
25871
|
.sp
|
25872
25872
|
geo_in_rectangle() 関数は、pointに指定した座標が、top_leftとbottom_rightがなす矩形の範囲内にあるかどうかを調べます。
|
25873
25873
|
.SS 引数
|
@@ -25915,10 +25915,10 @@ TokyoGeoPoint(日本測地系座標)かWGS84GeoPoint(世界測地系座標)の
|
|
25915
25915
|
.sp
|
25916
25916
|
\fBhtml_untag\fP strips HTML tags from HTML and outputs plain text.
|
25917
25917
|
.sp
|
25918
|
-
\fBhtml_untag\fP is used in \fB\-\-output_columns\fP described at \fIoutput_columns\fP
|
25918
|
+
\fBhtml_untag\fP is used in \fB\-\-output_columns\fP described at \fIoutput_columns\fP\&.
|
25919
25919
|
.SS Syntax
|
25920
25920
|
.sp
|
25921
|
-
\fBhtml_untag\fP requires only one argument. It is \fBhtml\fP
|
25921
|
+
\fBhtml_untag\fP requires only one argument. It is \fBhtml\fP\&.
|
25922
25922
|
.INDENT 0.0
|
25923
25923
|
.INDENT 3.5
|
25924
25924
|
.sp
|
@@ -25931,7 +25931,7 @@ html_untag(html)
|
|
25931
25931
|
.UNINDENT
|
25932
25932
|
.SS Requirements
|
25933
25933
|
.sp
|
25934
|
-
\fBhtml_untag\fP requires
|
25934
|
+
\fBhtml_untag\fP requires Groonga 3.0.5 or later.
|
25935
25935
|
.sp
|
25936
25936
|
\fBhtml_untag\fP requires \fB/reference/command/command_version\fP 2 or
|
25937
25937
|
later.
|
@@ -26019,7 +26019,7 @@ When executing the above query, you can see "span" tag with "class" attribute is
|
|
26019
26019
|
Note that you must specify \fB\-\-command_version 2\fP to use \fBhtml_untag\fP function.
|
26020
26020
|
.SS Parameters
|
26021
26021
|
.sp
|
26022
|
-
There is one required parameter, \fBhtml\fP
|
26022
|
+
There is one required parameter, \fBhtml\fP\&.
|
26023
26023
|
.SS \fBhtml\fP
|
26024
26024
|
.sp
|
26025
26025
|
It specifies HTML text to be untagged.
|
@@ -26043,7 +26043,7 @@ now()
|
|
26043
26043
|
.UNINDENT
|
26044
26044
|
.SS 説明
|
26045
26045
|
.sp
|
26046
|
-
|
26046
|
+
Groonga組込関数の一つであるnowについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
|
26047
26047
|
.sp
|
26048
26048
|
now() 関数は現在時刻に対応するTime型の値を返します。
|
26049
26049
|
.SS 返値
|
@@ -26067,16 +26067,16 @@ now()
|
|
26067
26067
|
\fBquery\fP provides \fB\-\-match_columns\fP and \fB\-\-query\fP parameters of
|
26068
26068
|
\fB/reference/commands/select\fP feature as function. You can specify
|
26069
26069
|
multiple \fBquery\fP functions in \fB\-\-filter\fP parameter in
|
26070
|
-
\fB/reference/commands/select\fP
|
26070
|
+
\fB/reference/commands/select\fP\&.
|
26071
26071
|
.sp
|
26072
26072
|
Because of such flexibility, you can control full text search behavior
|
26073
26073
|
by combination of multiple \fBquery\fP functions.
|
26074
26074
|
.sp
|
26075
26075
|
\fBquery\fP can be used in only \fB\-\-filter\fP in
|
26076
|
-
\fB/reference/commands/select\fP
|
26076
|
+
\fB/reference/commands/select\fP\&.
|
26077
26077
|
.SS Syntax
|
26078
26078
|
.sp
|
26079
|
-
\fBquery\fP requires two arguments \- \fBmatch_columns\fP and \fBquery_string\fP
|
26079
|
+
\fBquery\fP requires two arguments \- \fBmatch_columns\fP and \fBquery_string\fP\&.
|
26080
26080
|
.sp
|
26081
26081
|
The parameter \fBquery_expander\fP or \fBsubstitution_table\fP is optional.
|
26082
26082
|
.INDENT 0.0
|
@@ -26154,7 +26154,7 @@ load \-\-table Users
|
|
26154
26154
|
.sp
|
26155
26155
|
Here is the simple usage of \fBquery\fP function which execute full text
|
26156
26156
|
search by keyword \(aqalice\(aq without using \fB\-\-match_columns\fP and
|
26157
|
-
\fB\-\-query\fP arguments in \fB\-\-filter\fP
|
26157
|
+
\fB\-\-query\fP arguments in \fB\-\-filter\fP\&.
|
26158
26158
|
.sp
|
26159
26159
|
Execution example:
|
26160
26160
|
.INDENT 0.0
|
@@ -26199,7 +26199,7 @@ select Users \-\-output_columns name,_score \-\-filter \(aqquery("name * 10", "a
|
|
26199
26199
|
When executing above query, the keyword \(aqalice\(aq is weighted to the value \-
|
26200
26200
|
\(aq10\(aq.
|
26201
26201
|
.sp
|
26202
|
-
Here are the contrasting examples with/without \fBquery\fP
|
26202
|
+
Here are the contrasting examples with/without \fBquery\fP\&.
|
26203
26203
|
.sp
|
26204
26204
|
Execution example:
|
26205
26205
|
.INDENT 0.0
|
@@ -26343,20 +26343,20 @@ keywords on your purpose.
|
|
26343
26343
|
.SS Parameters
|
26344
26344
|
.SS Required parameter
|
26345
26345
|
.sp
|
26346
|
-
There are two required parameter, \fBmatch_columns\fP and \fBquery_string\fP
|
26346
|
+
There are two required parameter, \fBmatch_columns\fP and \fBquery_string\fP\&.
|
26347
26347
|
.SS \fBmatch_columns\fP
|
26348
26348
|
.sp
|
26349
26349
|
It specifies the default target column for fulltext search by
|
26350
26350
|
\fBquery_string\fP parameter value. It is the same role as
|
26351
|
-
\fIselect\-match\-columns\fP parameter in \fBselect\fP
|
26351
|
+
\fIselect\-match\-columns\fP parameter in \fBselect\fP\&.
|
26352
26352
|
.SS \fBquery_string\fP
|
26353
26353
|
.sp
|
26354
26354
|
It specifies the search condition in
|
26355
|
-
\fB/reference/grn_expr/query_syntax\fP
|
26356
|
-
\fBquery\fP parameter in \fBselect\fP
|
26355
|
+
\fB/reference/grn_expr/query_syntax\fP\&. It is the same role as
|
26356
|
+
\fBquery\fP parameter in \fBselect\fP\&.
|
26357
26357
|
.sp
|
26358
26358
|
See \fIselect\-match\-columns\fP about \fBquery\fP parameter in
|
26359
|
-
\fBselect\fP
|
26359
|
+
\fBselect\fP\&.
|
26360
26360
|
.SS Optional parameter
|
26361
26361
|
.sp
|
26362
26362
|
There are some optional parameters.
|
@@ -26364,7 +26364,7 @@ There are some optional parameters.
|
|
26364
26364
|
.sp
|
26365
26365
|
It specifies the plugin name for query expansion.
|
26366
26366
|
.sp
|
26367
|
-
There is one plugin bundled in official release \- \fB/reference/query_expanders/tsv\fP
|
26367
|
+
There is one plugin bundled in official release \- \fB/reference/query_expanders/tsv\fP\&.
|
26368
26368
|
.sp
|
26369
26369
|
See \fB/reference/query_expanders/tsv\fP about details.
|
26370
26370
|
.SS \fBsubstitution_table\fP
|
@@ -26376,8 +26376,8 @@ See \fIquery\-expander\fP about details.
|
|
26376
26376
|
.SS Return value
|
26377
26377
|
.sp
|
26378
26378
|
\fBquery\fP returns whether any record is matched or not. If one or more
|
26379
|
-
records are matched, it returns \fBtrue\fP
|
26380
|
-
\fBfalse\fP
|
26379
|
+
records are matched, it returns \fBtrue\fP\&. Otherwise, it returns
|
26380
|
+
\fBfalse\fP\&.
|
26381
26381
|
.SS TODO
|
26382
26382
|
.INDENT 0.0
|
26383
26383
|
.IP \(bu 2
|
@@ -26405,7 +26405,7 @@ rand([max])
|
|
26405
26405
|
.UNINDENT
|
26406
26406
|
.SS 説明
|
26407
26407
|
.sp
|
26408
|
-
|
26408
|
+
Groonga組込関数の一つであるrandについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
|
26409
26409
|
.sp
|
26410
26410
|
rand() 関数は 0 から max の間の疑似乱数整数を返します。
|
26411
26411
|
.SS 引数
|
@@ -26442,12 +26442,12 @@ This feature is experimental. API will be changed.
|
|
26442
26442
|
.SS Summary
|
26443
26443
|
.sp
|
26444
26444
|
\fBsnippet_html\fP extracts snippets of target text around search
|
26445
|
-
keywords (\fBKWIC\fP
|
26445
|
+
keywords (\fBKWIC\fP\&. \fBKeyWord In Context\fP). The snippets are prepared
|
26446
26446
|
for embedding HTML. Special characters such as \fB<\fP and \fB>\fP are
|
26447
|
-
escapsed as \fB<\fP and \fB>\fP
|
26448
|
-
class="keyword">\fP and \fB</span>\fP
|
26447
|
+
escapsed as \fB<\fP and \fB>\fP\&. Keyword is surrounded with \fB<span
|
26448
|
+
class="keyword">\fP and \fB</span>\fP\&. For example, a snippet of \fBI am a
|
26449
26449
|
groonga user. <3\fP for keyword \fBgroonga\fP is \fBI am a <span
|
26450
|
-
class="keyword">groonga</span> user. <3\fP
|
26450
|
+
class="keyword">groonga</span> user. <3\fP\&.
|
26451
26451
|
.SS Syntax
|
26452
26452
|
.sp
|
26453
26453
|
\fBsnippet_html\fP has only one parameter:
|
@@ -26495,16 +26495,16 @@ load \-\-table Documents
|
|
26495
26495
|
.UNINDENT
|
26496
26496
|
.sp
|
26497
26497
|
\fBsnippet_html\fP can be used in only \fB\-\-output_columns\fP in
|
26498
|
-
\fB/reference/commands/select\fP
|
26498
|
+
\fB/reference/commands/select\fP\&.
|
26499
26499
|
.sp
|
26500
26500
|
You need to specify \fB\-\-command_version 2\fP argument explicitly
|
26501
26501
|
because function call in \fB\-\-output_columns\fP is experimental feature
|
26502
|
-
in
|
26502
|
+
in Groonga 2.0.9. It will be enabled by default soon.
|
26503
26503
|
.sp
|
26504
|
-
You also need to specify \fB\-\-query\fP and/or \fB\-\-filter\fP
|
26504
|
+
You also need to specify \fB\-\-query\fP and/or \fB\-\-filter\fP\&. Keywords are
|
26505
26505
|
extracted from \fB\-\-query\fP and \fB\-\-filter\fP arguments.
|
26506
26506
|
.sp
|
26507
|
-
The following example uses \fB\-\-query "fast performance"\fP
|
26507
|
+
The following example uses \fB\-\-query "fast performance"\fP\&. In this
|
26508
26508
|
case, \fBfast\fP and \fBperformance\fP are used as keywords.
|
26509
26509
|
.sp
|
26510
26510
|
Execution example:
|
@@ -26548,14 +26548,14 @@ select Documents \-\-output_columns "snippet_html(content)" \-\-command_version
|
|
26548
26548
|
\fB\-\-query "fast performance"\fP matches to only the first record\(aqs
|
26549
26549
|
content. \fBsnippet_html(content)\fP extracts two text parts that
|
26550
26550
|
include the keywords \fBfast\fP or \fBperformance\fP and surronds the
|
26551
|
-
keywords with \fB<span class="keyword">\fP and \fB</span>\fP
|
26551
|
+
keywords with \fB<span class="keyword">\fP and \fB</span>\fP\&.
|
26552
26552
|
.sp
|
26553
26553
|
The max number of text parts is 3. If there are 4 or more text parts
|
26554
26554
|
that include the keywords, only the leading 3 parts are only used.
|
26555
26555
|
.sp
|
26556
26556
|
The max size of a text part is 200byte. The unit is bytes not
|
26557
26557
|
chracters. The size doesn\(aqt include inserted \fB<span keyword="keyword">\fP
|
26558
|
-
and \fB</span>\fP
|
26558
|
+
and \fB</span>\fP\&.
|
26559
26559
|
.sp
|
26560
26560
|
Both the max number of text parts and the max size of a text part
|
26561
26561
|
aren\(aqt customizable.
|
@@ -26600,8 +26600,10 @@ select Documents \-\-output_columns \(aqsnippet_html("Groonga is very fast fullt
|
|
26600
26600
|
.UNINDENT
|
26601
26601
|
.SS Return value
|
26602
26602
|
.sp
|
26603
|
-
\fBsnippet_html\fP returns an array of string
|
26604
|
-
|
26603
|
+
\fBsnippet_html\fP returns an array of string or \fBnull\fP\&. If
|
26604
|
+
\fBsnippet_html\fP can\(aqt find any snippets, it returns \fBnull\fP\&.
|
26605
|
+
.sp
|
26606
|
+
An element of array is a snippet:
|
26605
26607
|
.INDENT 0.0
|
26606
26608
|
.INDENT 3.5
|
26607
26609
|
.sp
|
@@ -26645,11 +26647,11 @@ Support options by object literal.
|
|
26645
26647
|
\fBsub_filter\fP evaluates \fBfilter_string\fP in \fBscope\fP context.
|
26646
26648
|
.sp
|
26647
26649
|
\fBsub_filter\fP can be used in only \fB\-\-filter\fP in
|
26648
|
-
\fB/reference/commands/select\fP
|
26650
|
+
\fB/reference/commands/select\fP\&.
|
26649
26651
|
.SS Syntax
|
26650
26652
|
.sp
|
26651
26653
|
\fBsub_filter\fP requires two arguments. They are \fBscope\fP and
|
26652
|
-
\fBfilter_string\fP
|
26654
|
+
\fBfilter_string\fP\&.
|
26653
26655
|
.INDENT 0.0
|
26654
26656
|
.INDENT 3.5
|
26655
26657
|
.sp
|
@@ -26828,32 +26830,32 @@ There are the records that user "A" mentions about "groonga".
|
|
26828
26830
|
.UNINDENT
|
26829
26831
|
.SS Parameters
|
26830
26832
|
.sp
|
26831
|
-
There are two required parameter, \fBscope\fP and \fBfilter_string\fP
|
26833
|
+
There are two required parameter, \fBscope\fP and \fBfilter_string\fP\&.
|
26832
26834
|
.SS \fBscope\fP
|
26833
26835
|
.sp
|
26834
26836
|
It specifies a column of the table that is specified by \fBtable\fP
|
26835
|
-
parameter in \fBselect\fP
|
26837
|
+
parameter in \fBselect\fP\&. The column has a limitation. The limitation
|
26836
26838
|
is described later. \fBfilter_string\fP is evaluated in the column
|
26837
26839
|
context. It means that \fBfilter_string\fP is evaluated like
|
26838
|
-
\fBselect \-\-table TYPE_OF_THE_COLUMN \-\-filter FILTER_STRING\fP
|
26840
|
+
\fBselect \-\-table TYPE_OF_THE_COLUMN \-\-filter FILTER_STRING\fP\&.
|
26839
26841
|
.sp
|
26840
26842
|
The specified column type must be a table. In other words, the column
|
26841
26843
|
type must be reference type.
|
26842
26844
|
.sp
|
26843
26845
|
You can chain columns by \fBCOLUMN_1.COLUMN_2.COLUMN_3...COLUMN_N\fP
|
26844
|
-
syntax. For example, \fBuser.group.name\fP
|
26846
|
+
syntax. For example, \fBuser.group.name\fP\&.
|
26845
26847
|
.sp
|
26846
|
-
See \fIselect\-table\fP about \fBtable\fP parameter in \fBselect\fP
|
26848
|
+
See \fIselect\-table\fP about \fBtable\fP parameter in \fBselect\fP\&.
|
26847
26849
|
.SS \fBfilter_string\fP
|
26848
26850
|
.sp
|
26849
26851
|
It specifies a search condition in
|
26850
|
-
\fB/reference/grn_expr/script_syntax\fP
|
26852
|
+
\fB/reference/grn_expr/script_syntax\fP\&. It is evaluated in \fBscope\fP
|
26851
26853
|
context.
|
26852
26854
|
.SS Return value
|
26853
26855
|
.sp
|
26854
26856
|
\fBsub_filter\fP returns whether any record is matched or not. If one or
|
26855
|
-
more records are matched, it returns \fBtrue\fP
|
26856
|
-
\fBfalse\fP
|
26857
|
+
more records are matched, it returns \fBtrue\fP\&. Otherwise, it returns
|
26858
|
+
\fBfalse\fP\&.
|
26857
26859
|
.SS See also
|
26858
26860
|
.INDENT 0.0
|
26859
26861
|
.IP \(bu 2
|
@@ -26977,7 +26979,7 @@ select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
|
|
26977
26979
|
.UNINDENT
|
26978
26980
|
.UNINDENT
|
26979
26981
|
.sp
|
26980
|
-
We create index for \fBTweets.content\fP
|
26982
|
+
We create index for \fBTweets.content\fP\&. Already registered
|
26981
26983
|
data in \fBTweets.content\fP are indexed by offline index
|
26982
26984
|
construction:
|
26983
26985
|
.sp
|
@@ -27112,7 +27114,7 @@ Process log is enabled by default. Log path can be
|
|
27112
27114
|
customized by \fI\-\-log\-path\fP option. Each log has its
|
27113
27115
|
log level. If a log is smaller than groonga process\(aq log
|
27114
27116
|
level, it\(aqs not logged. Log level can be customized by
|
27115
|
-
\fI\-l\fP or \fBcommands/log_level\fP
|
27117
|
+
\fI\-l\fP or \fBcommands/log_level\fP\&.
|
27116
27118
|
.SS Format
|
27117
27119
|
.sp
|
27118
27120
|
Process log uses the following format:
|
@@ -27449,7 +27451,7 @@ Example:
|
|
27449
27451
|
.SS Tuning
|
27450
27452
|
.SS Summary
|
27451
27453
|
.sp
|
27452
|
-
There are some tuning parameters for improving
|
27454
|
+
There are some tuning parameters for improving Groonga performance or
|
27453
27455
|
handling a large database.
|
27454
27456
|
.SS Parameters
|
27455
27457
|
.sp
|
@@ -27570,7 +27572,7 @@ or re\-login as your groonga user.
|
|
27570
27572
|
.sp
|
27571
27573
|
This is \fItuning\-memory\-usage\fP related parameter. You can handle a
|
27572
27574
|
database that is larger than your memory and swap by setting
|
27573
|
-
\fBvm.overcommit_memory\fP kernel parameter to 1. 1 means that
|
27575
|
+
\fBvm.overcommit_memory\fP kernel parameter to 1. 1 means that Groonga
|
27574
27576
|
can always map database files onto memory. It is no problem until
|
27575
27577
|
groonga touch mapped database files that their size is larger than
|
27576
27578
|
memory and swap. Groonga recommends the configuration.
|
@@ -27615,7 +27617,7 @@ than 16GiB, groonga reaches the limitation. (\fB256KiB * 65536 = 16GiB\fP)
|
|
27615
27617
|
.sp
|
27616
27618
|
You needs to increase the value of the kernel parameter to handle
|
27617
27619
|
16GiB or more larger size database. For example, you can handle almost
|
27618
|
-
32GiB size database by \fB65536 * 2 = 131072\fP
|
27620
|
+
32GiB size database by \fB65536 * 2 = 131072\fP\&. You can set the
|
27619
27621
|
configuration by putting a configuration file
|
27620
27622
|
\fB/etc/sysctl.d/groonga.conf\fP that has the following content:
|
27621
27623
|
.INDENT 0.0
|
@@ -27665,6 +27667,69 @@ TODO
|
|
27665
27667
|
.sp
|
27666
27668
|
Groonga can be used as a fulltext search library. This section
|
27667
27669
|
describes APIs that are provided by groonga.
|
27670
|
+
.SS Global configurations
|
27671
|
+
.SS Summary
|
27672
|
+
.sp
|
27673
|
+
Groonga has the global configurations. You can access them by API.
|
27674
|
+
.SS Reference
|
27675
|
+
.INDENT 0.0
|
27676
|
+
.TP
|
27677
|
+
.B int grn_get_lock_timeout(void)
|
27678
|
+
Returns the lock timeout.
|
27679
|
+
.sp
|
27680
|
+
\fBgrn_ctx\fP acquires a lock for updating a shared value. If
|
27681
|
+
other \fBgrn_ctx\fP is already updating the same value,
|
27682
|
+
\fBgrn_ctx\fP that try to acquire a lock can\(aqt acquires a lock.
|
27683
|
+
The \fBgrn_ctx\fP that can\(aqt acquires a lock waits 1
|
27684
|
+
millisecond and try to acquire a lock again. The try is done
|
27685
|
+
\fBtimeout\fP times. If the \fBgrn_ctx\fP that can\(aqt acquires a
|
27686
|
+
lock until \fBtimeout\fP times, the tries are failed.
|
27687
|
+
.sp
|
27688
|
+
The default lock timeout is \fB10000000\fP\&. It means that Groonga
|
27689
|
+
doesn\(aqt report a lock failure until about 3 hours. (1 * 10000000
|
27690
|
+
[msec] = 10000 [sec] = 166.666... [min] = 2.777... [hour])
|
27691
|
+
.INDENT 7.0
|
27692
|
+
.TP
|
27693
|
+
.B Returns
|
27694
|
+
The lock timeout.
|
27695
|
+
.UNINDENT
|
27696
|
+
.UNINDENT
|
27697
|
+
.INDENT 0.0
|
27698
|
+
.TP
|
27699
|
+
.B grn_rc grn_set_lock_timeout(int\fI\ timeout\fP)
|
27700
|
+
Sets the lock timeout.
|
27701
|
+
.sp
|
27702
|
+
See
|
27703
|
+
.nf
|
27704
|
+
:c:function:\(gagrn_get_lock_timeout\(ga
|
27705
|
+
.fi
|
27706
|
+
about lock timeout.
|
27707
|
+
.sp
|
27708
|
+
There are some special values for \fBtimeout\fP\&.
|
27709
|
+
.INDENT 7.0
|
27710
|
+
.INDENT 3.5
|
27711
|
+
.INDENT 0.0
|
27712
|
+
.IP \(bu 2
|
27713
|
+
\fB0\fP: It means that Groonga doesn\(aqt retry acquiring a lock.
|
27714
|
+
Groonga reports a failure after one lock acquirement failure.
|
27715
|
+
.IP \(bu 2
|
27716
|
+
negative value: It means that Groonga retries acquiring a lock
|
27717
|
+
until Groonga can acquire a lock.
|
27718
|
+
.UNINDENT
|
27719
|
+
.UNINDENT
|
27720
|
+
.UNINDENT
|
27721
|
+
.INDENT 7.0
|
27722
|
+
.TP
|
27723
|
+
.B Parameters
|
27724
|
+
.INDENT 7.0
|
27725
|
+
.IP \(bu 2
|
27726
|
+
\fBtimeuot\fP \-\- The new lock timeout.
|
27727
|
+
.UNINDENT
|
27728
|
+
.TP
|
27729
|
+
.B Returns
|
27730
|
+
\fBGRN_SUCCESS\fP\&. It doesn\(aqt fail.
|
27731
|
+
.UNINDENT
|
27732
|
+
.UNINDENT
|
27668
27733
|
.SS \fBgrn_cache\fP
|
27669
27734
|
.SS Summary
|
27670
27735
|
.sp
|
@@ -27680,7 +27745,7 @@ This API is experimental.
|
|
27680
27745
|
object. It is only for \fB/reference/commands/select\fP command.
|
27681
27746
|
.sp
|
27682
27747
|
You can just change the current cache object by
|
27683
|
-
\fBgrn_cache_current_set()\fP
|
27748
|
+
\fBgrn_cache_current_set()\fP\&. \fB/reference/commands/select\fP
|
27684
27749
|
command response cache is done internally.
|
27685
27750
|
.sp
|
27686
27751
|
\fB/reference/commands/select\fP command uses one global cache
|
@@ -27718,7 +27783,7 @@ grn_cache_current_set(ctx, cache_previous);
|
|
27718
27783
|
.B grn_cache
|
27719
27784
|
It is an opaque cache object. You can create a \fBgrn_cache\fP by
|
27720
27785
|
\fBgrn_cache_open()\fP and free the created object by
|
27721
|
-
\fBgrn_cache_close()\fP
|
27786
|
+
\fBgrn_cache_close()\fP\&.
|
27722
27787
|
.UNINDENT
|
27723
27788
|
.INDENT 0.0
|
27724
27789
|
.TP
|
@@ -27726,7 +27791,7 @@ It is an opaque cache object. You can create a \fBgrn_cache\fP by
|
|
27726
27791
|
Creates a new cache object.
|
27727
27792
|
.sp
|
27728
27793
|
If memory allocation for the new cache object is failed, \fBNULL\fP
|
27729
|
-
is returned. Error information is stored into the \fBctx\fP
|
27794
|
+
is returned. Error information is stored into the \fBctx\fP\&.
|
27730
27795
|
.INDENT 7.0
|
27731
27796
|
.TP
|
27732
27797
|
.B Parameters
|
@@ -27738,13 +27803,13 @@ is returned. Error information is stored into the \fBctx\fP.
|
|
27738
27803
|
.B Returns
|
27739
27804
|
A newly allocated cache object on success, \fBNULL\fP
|
27740
27805
|
otherwise. The returned cache object must be freed by
|
27741
|
-
\fBgrn_cache_close()\fP
|
27806
|
+
\fBgrn_cache_close()\fP\&.
|
27742
27807
|
.UNINDENT
|
27743
27808
|
.UNINDENT
|
27744
27809
|
.INDENT 0.0
|
27745
27810
|
.TP
|
27746
27811
|
.B grn_rc grn_cache_close(grn_ctx\fI\ *ctx\fP, grn_cache\fI\ *cache\fP)
|
27747
|
-
Frees resourses of the \fBcache\fP
|
27812
|
+
Frees resourses of the \fBcache\fP\&.
|
27748
27813
|
.INDENT 7.0
|
27749
27814
|
.TP
|
27750
27815
|
.B Parameters
|
@@ -27794,7 +27859,7 @@ Gets the cache object that is used in
|
|
27794
27859
|
.TP
|
27795
27860
|
.B Returns
|
27796
27861
|
The cache object that is used in
|
27797
|
-
\fB/reference/commands/select\fP command. It may be \fBNULL\fP
|
27862
|
+
\fB/reference/commands/select\fP command. It may be \fBNULL\fP\&.
|
27798
27863
|
.UNINDENT
|
27799
27864
|
.UNINDENT
|
27800
27865
|
.INDENT 0.0
|
@@ -27846,7 +27911,7 @@ TODO...
|
|
27846
27911
|
.INDENT 0.0
|
27847
27912
|
.TP
|
27848
27913
|
.B GRN_COLUMN_NAME_ID
|
27849
|
-
It returns the name of \fB/reference/pseudo_column\fP \fB_id\fP
|
27914
|
+
It returns the name of \fB/reference/pseudo_column\fP \fB_id\fP\&.
|
27850
27915
|
.sp
|
27851
27916
|
It is useful to use with \fBGRN_COLUMN_NAME_ID_LEN\fP like
|
27852
27917
|
the following:
|
@@ -27867,14 +27932,14 @@ Since 3.1.1.
|
|
27867
27932
|
.INDENT 0.0
|
27868
27933
|
.TP
|
27869
27934
|
.B GRN_COLUMN_NAME_ID_LEN
|
27870
|
-
It returns the byte size of \fBGRN_COLUMN_NAME_ID\fP
|
27935
|
+
It returns the byte size of \fBGRN_COLUMN_NAME_ID\fP\&.
|
27871
27936
|
.sp
|
27872
27937
|
Since 3.1.1.
|
27873
27938
|
.UNINDENT
|
27874
27939
|
.INDENT 0.0
|
27875
27940
|
.TP
|
27876
27941
|
.B GRN_COLUMN_NAME_KEY
|
27877
|
-
It returns the name of \fB/reference/pseudo_column\fP \fB_key\fP
|
27942
|
+
It returns the name of \fB/reference/pseudo_column\fP \fB_key\fP\&.
|
27878
27943
|
.sp
|
27879
27944
|
It is useful to use with \fBGRN_COLUMN_NAME_KEY_LEN\fP like
|
27880
27945
|
the following:
|
@@ -27895,14 +27960,14 @@ Since 3.1.1.
|
|
27895
27960
|
.INDENT 0.0
|
27896
27961
|
.TP
|
27897
27962
|
.B GRN_COLUMN_NAME_KEY_LEN
|
27898
|
-
It returns the byte size of \fBGRN_COLUMN_NAME_KEY\fP
|
27963
|
+
It returns the byte size of \fBGRN_COLUMN_NAME_KEY\fP\&.
|
27899
27964
|
.sp
|
27900
27965
|
Since 3.1.1.
|
27901
27966
|
.UNINDENT
|
27902
27967
|
.INDENT 0.0
|
27903
27968
|
.TP
|
27904
27969
|
.B GRN_COLUMN_NAME_VALUE
|
27905
|
-
It returns the name of \fB/reference/pseudo_column\fP \fB_value\fP
|
27970
|
+
It returns the name of \fB/reference/pseudo_column\fP \fB_value\fP\&.
|
27906
27971
|
.sp
|
27907
27972
|
It is useful to use with \fBGRN_COLUMN_NAME_VALUE_LEN\fP like
|
27908
27973
|
the following:
|
@@ -27923,14 +27988,14 @@ Since 3.1.1.
|
|
27923
27988
|
.INDENT 0.0
|
27924
27989
|
.TP
|
27925
27990
|
.B GRN_COLUMN_NAME_VALUE_LEN
|
27926
|
-
It returns the byte size of \fBGRN_COLUMN_NAME_VALUE\fP
|
27991
|
+
It returns the byte size of \fBGRN_COLUMN_NAME_VALUE\fP\&.
|
27927
27992
|
.sp
|
27928
27993
|
Since 3.1.1.
|
27929
27994
|
.UNINDENT
|
27930
27995
|
.INDENT 0.0
|
27931
27996
|
.TP
|
27932
27997
|
.B GRN_COLUMN_NAME_SCORE
|
27933
|
-
It returns the name of \fB/reference/pseudo_column\fP \fB_score\fP
|
27998
|
+
It returns the name of \fB/reference/pseudo_column\fP \fB_score\fP\&.
|
27934
27999
|
.sp
|
27935
28000
|
It is useful to use with \fBGRN_COLUMN_NAME_SCORE_LEN\fP like
|
27936
28001
|
the following:
|
@@ -27951,14 +28016,14 @@ Since 3.1.1.
|
|
27951
28016
|
.INDENT 0.0
|
27952
28017
|
.TP
|
27953
28018
|
.B GRN_COLUMN_NAME_SCORE_LEN
|
27954
|
-
It returns the byte size of \fBGRN_COLUMN_NAME_SCORE\fP
|
28019
|
+
It returns the byte size of \fBGRN_COLUMN_NAME_SCORE\fP\&.
|
27955
28020
|
.sp
|
27956
28021
|
Since 3.1.1.
|
27957
28022
|
.UNINDENT
|
27958
28023
|
.INDENT 0.0
|
27959
28024
|
.TP
|
27960
28025
|
.B GRN_COLUMN_NAME_NSUBRECS
|
27961
|
-
It returns the name of \fB/reference/pseudo_column\fP \fB_nsubrecs\fP
|
28026
|
+
It returns the name of \fB/reference/pseudo_column\fP \fB_nsubrecs\fP\&.
|
27962
28027
|
.sp
|
27963
28028
|
It is useful to use with \fBGRN_COLUMN_NAME_NSUBRECS_LEN\fP like
|
27964
28029
|
the following:
|
@@ -27979,7 +28044,7 @@ Since 3.1.1.
|
|
27979
28044
|
.INDENT 0.0
|
27980
28045
|
.TP
|
27981
28046
|
.B GRN_COLUMN_NAME_NSUBRECS_LEN
|
27982
|
-
It returns the byte size of \fBGRN_COLUMN_NAME_NSUBRECS\fP
|
28047
|
+
It returns the byte size of \fBGRN_COLUMN_NAME_NSUBRECS\fP\&.
|
27983
28048
|
.sp
|
27984
28049
|
Since 3.1.1.
|
27985
28050
|
.UNINDENT
|
@@ -28220,7 +28285,7 @@ ctxを初期化します。
|
|
28220
28285
|
.B grn_rc grn_ctx_fin(grn_ctx\fI\ *ctx\fP)
|
28221
28286
|
ctxの管理するメモリを解放し、使用を終了します。
|
28222
28287
|
.sp
|
28223
|
-
If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP
|
28288
|
+
If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP\&. You need also to call \fBgrn_ctx_close()\fP\&.
|
28224
28289
|
.INDENT 7.0
|
28225
28290
|
.TP
|
28226
28291
|
.B Parameters
|
@@ -28256,13 +28321,13 @@ If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP. Yo
|
|
28256
28321
|
.INDENT 0.0
|
28257
28322
|
.TP
|
28258
28323
|
.B grn_rc grn_ctx_close(grn_ctx\fI\ *ctx\fP)
|
28259
|
-
It calls \fBgrn_ctx_fin()\fP and frees allocated memory for \fBctx\fP by \fBgrn_ctx_open()\fP
|
28324
|
+
It calls \fBgrn_ctx_fin()\fP and frees allocated memory for \fBctx\fP by \fBgrn_ctx_open()\fP\&.
|
28260
28325
|
.INDENT 7.0
|
28261
28326
|
.TP
|
28262
28327
|
.B Parameters
|
28263
28328
|
.INDENT 7.0
|
28264
28329
|
.IP \(bu 2
|
28265
|
-
\fBctx\fP \-\- no longer needed \fBgrn_ctx\fP
|
28330
|
+
\fBctx\fP \-\- no longer needed \fBgrn_ctx\fP\&.
|
28266
28331
|
.UNINDENT
|
28267
28332
|
.TP
|
28268
28333
|
.B Returns
|
@@ -28371,7 +28436,7 @@ TODO...
|
|
28371
28436
|
.INDENT 0.0
|
28372
28437
|
.TP
|
28373
28438
|
.B grn_db_create_optarg
|
28374
|
-
It is used for specifying options for \fBgrn_db_create()\fP
|
28439
|
+
It is used for specifying options for \fBgrn_db_create()\fP\&.
|
28375
28440
|
.UNINDENT
|
28376
28441
|
.INDENT 0.0
|
28377
28442
|
.TP
|
@@ -28519,7 +28584,7 @@ is a list of what expression can do:
|
|
28519
28584
|
.INDENT 0.0
|
28520
28585
|
.IP \(bu 2
|
28521
28586
|
Expression can apply some operations to a record by
|
28522
|
-
\fBgrn_expr_exec()\fP
|
28587
|
+
\fBgrn_expr_exec()\fP\&.
|
28523
28588
|
.IP \(bu 2
|
28524
28589
|
Expression can represents search condition. \fBgrn_table_select()\fP
|
28525
28590
|
can select records that match against the search condition represented
|
@@ -28585,31 +28650,31 @@ TODO...
|
|
28585
28650
|
.INDENT 0.0
|
28586
28651
|
.TP
|
28587
28652
|
.B grn_rc grn_expr_syntax_escape(grn_ctx\fI\ *ctx\fP, const char\fI\ *string\fP, int\fI\ string_size\fP, const char\fI\ *target_characters\fP, char\fI\ escape_character\fP, grn_obj\fI\ *escaped_string\fP)
|
28588
|
-
Escapes \fBtarget_characters\fP in \fBstring\fP by \fBescape_character\fP
|
28653
|
+
Escapes \fBtarget_characters\fP in \fBstring\fP by \fBescape_character\fP\&.
|
28589
28654
|
.INDENT 7.0
|
28590
28655
|
.TP
|
28591
28656
|
.B Parameters
|
28592
28657
|
.INDENT 7.0
|
28593
28658
|
.IP \(bu 2
|
28594
|
-
\fBctx\fP \-\- Its encoding must be the same encoding of \fBstring\fP
|
28595
|
-
It is used for allocating buffer for \fBescaped_string\fP
|
28659
|
+
\fBctx\fP \-\- Its encoding must be the same encoding of \fBstring\fP\&.
|
28660
|
+
It is used for allocating buffer for \fBescaped_string\fP\&.
|
28596
28661
|
.IP \(bu 2
|
28597
28662
|
\fBstring\fP \-\- String expression representation.
|
28598
28663
|
.IP \(bu 2
|
28599
|
-
\fBstring_size\fP \-\- The byte size of \fBstring\fP
|
28664
|
+
\fBstring_size\fP \-\- The byte size of \fBstring\fP\&. \fB\-1\fP means \fBstring\fP
|
28600
28665
|
is NULL terminated string.
|
28601
28666
|
.IP \(bu 2
|
28602
28667
|
\fBtarget_characters\fP \-\- NULL terminated escape target characters.
|
28603
28668
|
For example, \fB"+\-><~*()\e"\e\e:"\fP is
|
28604
28669
|
\fBtarget_characters\fP for
|
28605
|
-
\fB/reference/grn_expr/query_syntax\fP
|
28670
|
+
\fB/reference/grn_expr/query_syntax\fP\&.
|
28606
28671
|
.IP \(bu 2
|
28607
28672
|
\fBescape_character\fP \-\- The character to use escape a character in
|
28608
|
-
\fBtarget_characters\fP
|
28673
|
+
\fBtarget_characters\fP\&. For example, \fB\e\e\fP
|
28609
28674
|
(backslash) is \fBescaped_character\fP for
|
28610
|
-
\fB/reference/grn_expr/query_syntax\fP
|
28675
|
+
\fB/reference/grn_expr/query_syntax\fP\&.
|
28611
28676
|
.IP \(bu 2
|
28612
|
-
\fBescaped_string\fP \-\- The output of escaped \fBstring\fP
|
28677
|
+
\fBescaped_string\fP \-\- The output of escaped \fBstring\fP\&. It should be
|
28613
28678
|
text typed bulk.
|
28614
28679
|
.UNINDENT
|
28615
28680
|
.TP
|
@@ -28621,22 +28686,22 @@ text typed bulk.
|
|
28621
28686
|
.TP
|
28622
28687
|
.B grn_rc grn_expr_syntax_escape_query(grn_ctx\fI\ *ctx\fP, const char\fI\ *query\fP, int\fI\ query_size\fP, grn_obj\fI\ *escaped_query\fP)
|
28623
28688
|
Escapes special characters in
|
28624
|
-
\fB/reference/grn_expr/query_syntax\fP
|
28689
|
+
\fB/reference/grn_expr/query_syntax\fP\&.
|
28625
28690
|
.INDENT 7.0
|
28626
28691
|
.TP
|
28627
28692
|
.B Parameters
|
28628
28693
|
.INDENT 7.0
|
28629
28694
|
.IP \(bu 2
|
28630
|
-
\fBctx\fP \-\- Its encoding must be the same encoding of \fBquery\fP
|
28631
|
-
It is used for allocating buffer for \fBescaped_query\fP
|
28695
|
+
\fBctx\fP \-\- Its encoding must be the same encoding of \fBquery\fP\&.
|
28696
|
+
It is used for allocating buffer for \fBescaped_query\fP\&.
|
28632
28697
|
.IP \(bu 2
|
28633
28698
|
\fBquery\fP \-\- String expression representation in
|
28634
|
-
\fB/reference/grn_expr/query_syntax\fP
|
28699
|
+
\fB/reference/grn_expr/query_syntax\fP\&.
|
28635
28700
|
.IP \(bu 2
|
28636
|
-
\fBquery_size\fP \-\- The byte size of \fBquery\fP
|
28701
|
+
\fBquery_size\fP \-\- The byte size of \fBquery\fP\&. \fB\-1\fP means \fBquery\fP
|
28637
28702
|
is NULL terminated string.
|
28638
28703
|
.IP \(bu 2
|
28639
|
-
\fBescaped_query\fP \-\- The output of escaped \fBquery\fP
|
28704
|
+
\fBescaped_query\fP \-\- The output of escaped \fBquery\fP\&. It should be
|
28640
28705
|
text typed bulk.
|
28641
28706
|
.UNINDENT
|
28642
28707
|
.TP
|
@@ -31075,37 +31140,37 @@ Then save the configuration value to /etc/sysctl.conf or /etc/sysctl.d/
|
|
31075
31140
|
.nf
|
31076
31141
|
*
|
31077
31142
|
.fi
|
31078
|
-
|
31143
|
+
\&.conf.
|
31079
31144
|
.sp
|
31080
31145
|
See \fB/reference/tuning\fP documentation about tuning related parameters.
|
31081
31146
|
.SH DEVELOPMENT
|
31082
31147
|
.sp
|
31083
|
-
This section describes about developing with
|
31084
|
-
an application that uses
|
31148
|
+
This section describes about developing with Groonga. You may develop
|
31149
|
+
an application that uses Groonga as its database, a library that uses
|
31085
31150
|
libgroonga, language bindings of libgroonga and so on.
|
31086
31151
|
.SS Travis CI
|
31087
31152
|
.sp
|
31088
|
-
This section describes about using
|
31153
|
+
This section describes about using Groonga on \fI\%Travis CI\fP\&. Travis CI is a hosted continuous
|
31089
31154
|
integration service for the open source community.
|
31090
31155
|
.sp
|
31091
31156
|
You can use Travis CI for your open source software. This section only
|
31092
|
-
describes about
|
31157
|
+
describes about Groonga related configuration. See \fI\%Travis CI:
|
31093
31158
|
Documentation\fP about general
|
31094
31159
|
Travis CI.
|
31095
31160
|
.SS Configuration
|
31096
31161
|
.sp
|
31097
31162
|
Travis CI is running on 64\-bit Ubuntu 12.04 LTS Server Edition. (See \fI\%Travis CI: About
|
31098
|
-
Travis CI Environment\fP
|
31099
|
-
use apt\-line for Ubuntu 12.04 LTS provided by
|
31100
|
-
|
31163
|
+
Travis CI Environment\fP\&.) You can
|
31164
|
+
use apt\-line for Ubuntu 12.04 LTS provided by Groonga project to install
|
31165
|
+
Groonga on Travis CI.
|
31101
31166
|
.sp
|
31102
|
-
You can custom build lifecycle by \fB
|
31103
|
-
Conifugration your Travis CI build with .travis.yml\fP
|
31167
|
+
You can custom build lifecycle by \fB\&.travis.yml\fP\&. (See \fI\%Travis CI:
|
31168
|
+
Conifugration your Travis CI build with .travis.yml\fP\&.) You
|
31104
31169
|
can use \fBbefore_install\fP hook or \fBinstall\fP hook. You should use
|
31105
31170
|
\fBbefore_install\fP if your software uses a language that is supported
|
31106
31171
|
by Travis CI such as Ruby. You should use \fBinstall\fP otherwise.
|
31107
31172
|
.sp
|
31108
|
-
Add the following \fBbefore_install\fP configuration to \fB
|
31173
|
+
Add the following \fBbefore_install\fP configuration to \fB\&.travis.yml\fP:
|
31109
31174
|
.INDENT 0.0
|
31110
31175
|
.INDENT 3.5
|
31111
31176
|
.sp
|
@@ -31119,12 +31184,12 @@ before_install:
|
|
31119
31184
|
.UNINDENT
|
31120
31185
|
.sp
|
31121
31186
|
If you need to use \fBinstall\fP hook instead of \fBbefore_install\fP, you
|
31122
|
-
just substitute \fBbefore_install:\fP with \fBinstall:\fP
|
31187
|
+
just substitute \fBbefore_install:\fP with \fBinstall:\fP\&.
|
31123
31188
|
.sp
|
31124
|
-
With the above configuration, you can use
|
31189
|
+
With the above configuration, you can use Groonga for your build.
|
31125
31190
|
.SS Examples
|
31126
31191
|
.sp
|
31127
|
-
Here are open source softwares that use
|
31192
|
+
Here are open source softwares that use Groonga on Travis CI:
|
31128
31193
|
.INDENT 0.0
|
31129
31194
|
.INDENT 3.5
|
31130
31195
|
.INDENT 0.0
|
@@ -31134,7 +31199,7 @@ Here are open source softwares that use groonga on Travis CI:
|
|
31134
31199
|
.IP \(bu 2
|
31135
31200
|
\fI\%rroonga on Travis CI\fP
|
31136
31201
|
.IP \(bu 2
|
31137
|
-
\fI
|
31202
|
+
\fI\%\&.travis.yml for rroonga\fP
|
31138
31203
|
.UNINDENT
|
31139
31204
|
.IP \(bu 2
|
31140
31205
|
\fI\%nroonga\fP (node.js bindings)
|
@@ -31142,7 +31207,7 @@ Here are open source softwares that use groonga on Travis CI:
|
|
31142
31207
|
.IP \(bu 2
|
31143
31208
|
\fI\%nroonga on Travis CI\fP
|
31144
31209
|
.IP \(bu 2
|
31145
|
-
\fI
|
31210
|
+
\fI\%\&.travis.yml for nroonga\fP
|
31146
31211
|
.UNINDENT
|
31147
31212
|
.IP \(bu 2
|
31148
31213
|
\fI\%logaling\-command\fP (A glossary management command line tool)
|
@@ -31150,7 +31215,7 @@ Here are open source softwares that use groonga on Travis CI:
|
|
31150
31215
|
.IP \(bu 2
|
31151
31216
|
\fI\%logaling\-command on Travis CI\fP
|
31152
31217
|
.IP \(bu 2
|
31153
|
-
\fI
|
31218
|
+
\fI\%\&.travis.yml for logaling\-command\fP
|
31154
31219
|
.UNINDENT
|
31155
31220
|
.UNINDENT
|
31156
31221
|
.UNINDENT
|
@@ -31191,7 +31256,7 @@ You can use either way It makes no difference to us.
|
|
31191
31256
|
.SS Submit a bug to the issue tracker
|
31192
31257
|
.sp
|
31193
31258
|
Groonga project has two issue tracking systems, \fI\%Redmine\fP and \fI\%GitHub
|
31194
|
-
issue tracker\fP
|
31259
|
+
issue tracker\fP\&. Redmine
|
31195
31260
|
is for Japanese and GitHub issue tracker is for English. You can use
|
31196
31261
|
one of them to report a bug.
|
31197
31262
|
.SS Report a bug to the mailing list
|
@@ -31211,7 +31276,7 @@ We will use \fI\%the C domain markup\fP of Sphinx.
|
|
31211
31276
|
.SS I18N
|
31212
31277
|
.sp
|
31213
31278
|
We only had documentation in Japanese. We start to support
|
31214
|
-
I18N documentation by gettext based \fI\%Sphinx I18N feature\fP
|
31279
|
+
I18N documentation by gettext based \fI\%Sphinx I18N feature\fP\&.
|
31215
31280
|
We\(aqll use English as base language and translate
|
31216
31281
|
English into other languages such as Japanese. We\(aqll put
|
31217
31282
|
all documentations into doc/source/ and process them by
|
@@ -31368,7 +31433,7 @@ running \fImake html\fP on doc/locale:
|
|
31368
31433
|
\fBNOTE:\fP
|
31369
31434
|
.INDENT 0.0
|
31370
31435
|
.INDENT 3.5
|
31371
|
-
|
31436
|
+
\&.mo files are updated automatically by \fImake html\fP\&. So
|
31372
31437
|
you don\(aqt care about .mo files.
|
31373
31438
|
.UNINDENT
|
31374
31439
|
.UNINDENT
|
@@ -31415,7 +31480,7 @@ button.
|
|
31415
31480
|
\fBSEE ALSO:\fP
|
31416
31481
|
.INDENT 0.0
|
31417
31482
|
.INDENT 3.5
|
31418
|
-
\fI\%Help.GitHub \- Sending pull requests\fP
|
31483
|
+
\fI\%Help.GitHub \- Sending pull requests\fP\&.
|
31419
31484
|
.UNINDENT
|
31420
31485
|
.UNINDENT
|
31421
31486
|
.SS How to send patch
|
@@ -31477,13 +31542,13 @@ as \(aqja\(aq.
|
|
31477
31542
|
\fBSEE ALSO:\fP
|
31478
31543
|
.INDENT 0.0
|
31479
31544
|
.INDENT 3.5
|
31480
|
-
\fI\%Codes for the Representation of Names of Languages\fP
|
31545
|
+
\fI\%Codes for the Representation of Names of Languages\fP\&.
|
31481
31546
|
.UNINDENT
|
31482
31547
|
.UNINDENT
|
31483
31548
|
.SS groonga開発者向け情報
|
31484
31549
|
.SS Repository
|
31485
31550
|
.sp
|
31486
|
-
There is \fI\%the repository of groonga on GitHub\fP
|
31551
|
+
There is \fI\%the repository of groonga on GitHub\fP\&. If you want to check\-out groonga, type the below command:
|
31487
31552
|
.INDENT 0.0
|
31488
31553
|
.INDENT 3.5
|
31489
31554
|
.sp
|
@@ -33143,6 +33208,6 @@ configureは1度のみ実行する必要があります。
|
|
33143
33208
|
.SH AUTHOR
|
33144
33209
|
Groonga Project
|
33145
33210
|
.SH COPYRIGHT
|
33146
|
-
2009-
|
33211
|
+
2009-2014, Brazil, Inc
|
33147
33212
|
.\" Generated by docutils manpage writer.
|
33148
33213
|
.
|