[Groonga-commit] droonga/droonga-engine at 4c7a397 [master] Add news topics for compatibility around Groonga's `table_create` and `column_list`

Back to archive index

YUKI Hiroshi null+****@clear*****
Fri Nov 7 16:39:33 JST 2014


YUKI Hiroshi	2014-11-07 16:39:33 +0900 (Fri, 07 Nov 2014)

  New Revision: 4c7a397a46c660f969949e727f3a8475ef3e9bb8
  https://github.com/droonga/droonga-engine/commit/4c7a397a46c660f969949e727f3a8475ef3e9bb8

  Message:
    Add news topics for compatibility around Groonga's `table_create` and `column_list`

  Modified files:
    doc/text/news.md

  Modified: doc/text/news.md (+5 -0)
===================================================================
--- doc/text/news.md    2014-11-07 16:30:53 +0900 (2bd3ac4)
+++ doc/text/news.md    2014-11-07 16:39:33 +0900 (20b7748)
@@ -5,6 +5,11 @@
  * Better compatibility to Groonga's `select` command:
    * Whitespace-separeted `outout_columns` (it is valid on `command_version=1` environments) is now available.
    * `output_columns=*` works correctly even if it is a `TABLE_NO_KEY` table.
+ * Better compatibility to Groonga's `column_list` command:
+   * A `_key` virtual column is correctly appear in the result, for tables with one of flags: `TABLE_HASH_KEY`, `TABLE_PAT_KEY`, and `TABLE_DAT_KEY`.
+ * Groonga's `table_create` command now requires `key_type` parameter for tables with one of flags: `TABLE_HASH_KEY`, `TABLE_PAT_KEY`, or `TABLE_DAT_KEY`.
+   You'll get an error response, if the parameter is not given.
+   (Groonga unexpectedly accepts `table_create` requests without `key_type`, but it is a bad behavior (too lazy) and it should not be covered as a compatibility.)
  * The `daemon` option is now ignored in the static configuration file.
    Now, you always have to specify `--daemon` option for the `droonga-engine` command
    to start it as a daemon.
-------------- next part --------------
HTML����������������������������...
下載 



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