Kentaro Hayashi 2019-07-31 18:14:51 +0900 (Wed, 31 Jul 2019) Revision: f943ebd2cc5b5dd9d86a0c11790eb76a9ef8139f https://github.com/mroonga/mroonga.github.com/commit/f943ebd2cc5b5dd9d86a0c11790eb76a9ef8139f Message: blog en: use appropriate word Modified files: en/_posts/2019-07-30-mroonga-9.05.md Modified: en/_posts/2019-07-30-mroonga-9.05.md (+2 -2) =================================================================== --- en/_posts/2019-07-30-mroonga-9.05.md 2019-07-31 14:29:12 +0900 (4fa2709) +++ en/_posts/2019-07-30-mroonga-9.05.md 2019-07-31 18:14:51 +0900 (5318399) @@ -29,7 +29,7 @@ Note that if you already created an unique index, you must recreate target table In this release, added support for MySQL 5.6.45, 5.7.27 and 8.0.17. For MySQL 8.0, TIMESTAMP data type is supported. -MySQL 8.0 support is still in experimental stage, so if you found a bug or doubt behavior, please report to us! +MySQL 8.0 support is still in experimental stage, so if you found a bug or suspicious behavior, please report to us! Here is the documentation about "How to report a bug". @@ -68,7 +68,7 @@ MySQL [test]> INSERT INTO fts_targets (source_id, source_type_id) VALUES (10, 10 ERROR 1062 (23000): Duplicate entry '10-100' for key 'source_id' ``` -In above example, old index entry was not deleted correctly, therefore duplicated key error was occurred. +In above example, the old index entry was not deleted correctly, therefore duplicated key error was occurred. In this case, you must recreate an target table because unique index may have garbage entries. We recommend to recreate an target table with dump and restore, or execute the following queries. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.osdn.me/mailman/archives/groonga-mysql-commit/attachments/20190731/6ca3542b/attachment.html>
