cosmo0920
null+****@clear*****
Thu Dec 26 22:28:04 JST 2013
cosmo0920 2013-12-26 22:28:04 +0900 (Thu, 26 Dec 2013) New Revision: 196a33c15cbcca9416e8d17aa530c3dcf099ecba https://github.com/groonga/groonga/commit/196a33c15cbcca9416e8d17aa530c3dcf099ecba Merged 71be666: Merge pull request #140 from cosmo0920/use-Groonga-notation-reference Message: doc commands/reference.txt: use "Groonga" notation Modified files: doc/source/reference/commands/table_create.txt Modified: doc/source/reference/commands/table_create.txt (+2 -2) =================================================================== --- doc/source/reference/commands/table_create.txt 2013-12-26 22:06:52 +0900 (69994e8) +++ doc/source/reference/commands/table_create.txt 2013-12-26 22:28:04 +0900 (49da9a5) @@ -52,7 +52,7 @@ and is ``TABLE_NO_KEY`` type. If your records aren't searched by key, ``TABLE_NO_KEY`` type table is suitable. Because ``TABLE_NO_KEY`` doesn't support key but it is fast -and small table. Storing logs into groonga database is the case. +and small table. Storing logs into Groonga database is the case. If your records are searched by key or referenced by one or more columns, ``TABLE_NO_KEY`` type isn't suitable. Lexicon for fulltext @@ -198,7 +198,7 @@ Here are available flags: +--------------------+------------------------------+ .. note:: - Since groonga 2.1.0 ``KEY_NORMALIZE`` flag is deprecated. Use + Since Groonga 2.1.0 ``KEY_NORMALIZE`` flag is deprecated. Use ``normalizer`` option with ``NormalizerAuto`` instead. You must specify one of ``TABLE_${TYPE}`` flags. You cannot specify two -------------- next part -------------- HTML����������������������������...Download