# -*- po -*-
# English translations for Mroonga package.
# Copyright (C) 2009-2026, Mroonga Project
# This file is distributed under the same license as the Mroonga package.
# Automatically generated, 2026.
#
msgid ""
msgstr ""
"Project-Id-Version: Mroonga mrn_version\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2026-03-30 08:04+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: en\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "Optimizations"
msgstr "Optimizations"

msgid "Mroonga implemented some optimizations to return response faster."
msgstr "Mroonga implemented some optimizations to return response faster."

msgid "Some optimizations can work only on :doc:`/tutorial/storage`."
msgstr "Some optimizations can work only on :doc:`/tutorial/storage`."

msgid "Fetching only needed columns"
msgstr "Fetching only needed columns"

msgid "This optimization can work only on :doc:`/tutorial/storage`."
msgstr "This optimization can work only on :doc:`/tutorial/storage`."

msgid ""
"Groonga uses column store architecture. It means that Groonga doesn't need "
"to fetch values of all columns for fetching a column value in a row. Groonga "
"can fetch values of only needed columns."
msgstr ""
"Groonga uses column store architecture. It means that Groonga doesn't need "
"to fetch values of all columns for fetching a column value in a row. Groonga "
"can fetch values of only needed columns."

msgid ""
"InnoDB and MyISAM use row store architecture. They need to fetch values of "
"all columns for fetching a column value in a row."
msgstr ""
"InnoDB and MyISAM use row store architecture. They need to fetch values of "
"all columns for fetching a column value in a row."

msgid ""
"If you specify only columns you needed in ``SELECT``, Mroonga just fetches "
"only values of these columns. Mroonga doesn't fetch values of other columns."
msgstr ""
"If you specify only columns you needed in ``SELECT``, Mroonga just fetches "
"only values of these columns. Mroonga doesn't fetch values of other columns."

msgid "Mroonga can work faster by reducing operations and I/O."
msgstr "Mroonga can work faster by reducing operations and I/O."

msgid "It's this optimization."
msgstr "It's this optimization."

msgid "Here is a sample table definition to describe this optimization::"
msgstr "Here is a sample table definition to describe this optimization::"

msgid "Here is a ``SELECT`` to describe this optimization::"
msgstr "Here is a ``SELECT`` to describe this optimization::"

msgid ""
"In this case, Mroonga fetches values from only ``c1``, ``c2``, ``c11`` and "
"``c12``. Mroonga doesn't fetch values from ``c3``, ``c4``, ..., ``c10``, "
"``c13``, ..., ``c19`` and ``c20``."
msgstr ""
"In this case, Mroonga fetches values from only ``c1``, ``c2``, ``c11`` and "
"``c12``. Mroonga doesn't fetch values from ``c3``, ``c4``, ..., ``c10``, "
"``c13``, ..., ``c19`` and ``c20``."

msgid "Row count"
msgstr "Row count"

msgid ""
"MySQL requires all column values from storage engine for processing "
"``COUNT(*)`` even if ``COUNT(*)`` doesn't need them."
msgstr ""
"MySQL requires all column values from storage engine for processing "
"``COUNT(*)`` even if ``COUNT(*)`` doesn't need them."

msgid "Mroonga doesn't fetch any column values for the case."
msgstr "Mroonga doesn't fetch any column values for the case."

msgid ""
"The ``SELECT`` fetches only ``COUNT(*)`` and condition in ``WHERE`` can be "
"processed only by index. In this case, Mroonga uses this optimization."
msgstr ""
"The ``SELECT`` fetches only ``COUNT(*)`` and condition in ``WHERE`` can be "
"processed only by index. In this case, Mroonga uses this optimization."

msgid ""
"You can confirm whether this optimization is used or not by looking :ref:"
"`status-variable-mroonga-count-skip` status variable::"
msgstr ""
"You can confirm whether this optimization is used or not by looking :ref:"
"`status-variable-mroonga-count-skip` status variable::"

msgid ""
":ref:`status-variable-mroonga-count-skip` status variable is incremented "
"when Mroonga uses this optimization."
msgstr ""
":ref:`status-variable-mroonga-count-skip` status variable is incremented "
"when Mroonga uses this optimization."

msgid ""
"You can disable this optimization by setting :ref:`server-variable-mroonga-"
"enable-optimization` to ``false``."
msgstr ""
"You can disable this optimization by setting :ref:`server-variable-mroonga-"
"enable-optimization` to ``false``."

msgid "``ORDER BY LIMIT``"
msgstr "``ORDER BY LIMIT``"

msgid ""
"This optimization can work on both :doc:`/tutorial/storage` and :doc:`/"
"tutorial/wrapper`."
msgstr ""
"This optimization can work on both :doc:`/tutorial/storage` and :doc:`/"
"tutorial/wrapper`."

msgid ""
"MySQL can process ``ORDER BY`` and ``LIMIT`` with low cost if you can get "
"sorted records by index even if the number of matched records is very big."
msgstr ""
"MySQL can process ``ORDER BY`` and ``LIMIT`` with low cost if you can get "
"sorted records by index even if the number of matched records is very big."

msgid ""
"MySQL can do the process for ``MATCH() AGAINST(IN NATURAL LANGUAGE MODE)``. "
"But MySQL can't do the process for ``MATCH() AGAINST(IN BOOLEAN MODE)``."
msgstr ""
"MySQL can do the process for ``MATCH() AGAINST(IN NATURAL LANGUAGE MODE)``. "
"But MySQL can't do the process for ``MATCH() AGAINST(IN BOOLEAN MODE)``."

msgid ""
"It means that MySQL might take long time for ``MATCH() AGAINST(IN BOOLEAN "
"MODE)`` that matches with many records."
msgstr ""
"It means that MySQL might take long time for ``MATCH() AGAINST(IN BOOLEAN "
"MODE)`` that matches with many records."

msgid ""
"Mroonga processes ``ORDER BY`` and ``LIMIT`` by Groonga and returns only "
"target records to MySQL. It's very faster for query that matches with many "
"records."
msgstr ""
"Mroonga processes ``ORDER BY`` and ``LIMIT`` by Groonga and returns only "
"target records to MySQL. It's very faster for query that matches with many "
"records."

msgid ""
"The ``SELECT`` runs full text search and sorts by Groonga and returns only "
"one record to MySQL."
msgstr ""
"The ``SELECT`` runs full text search and sorts by Groonga and returns only "
"one record to MySQL."

msgid ""
"You can confirm whether this optimization is used or not by looking :ref:"
"`status-variable-mroonga-fast-order-limit` status variable::"
msgstr ""
"You can confirm whether this optimization is used or not by looking :ref:"
"`status-variable-mroonga-fast-order-limit` status variable::"

msgid ""
":ref:`status-variable-mroonga-fast-order-limit` status variable is "
"incremented when Mroonga uses this optimization."
msgstr ""
":ref:`status-variable-mroonga-fast-order-limit` status variable is "
"incremented when Mroonga uses this optimization."

msgid ""
"This optimization is used only when all the following conditions are true:"
msgstr ""
"This optimization is used only when all the following conditions are true:"

msgid ""
":doc:`/tutorial/storage`: ``WHERE`` clause has one ``MATCH AGAINST`` and "
"zero or more arithmetic operations such as ``column < 100``."
msgstr ""
":doc:`/tutorial/storage`: ``WHERE`` clause has one ``MATCH AGAINST`` and "
"zero or more arithmetic operations such as ``column < 100``."

msgid ":doc:`/tutorial/wrapper`: ``WHERE`` clause has only ``MATCH AGAINST``."
msgstr ":doc:`/tutorial/wrapper`: ``WHERE`` clause has only ``MATCH AGAINST``."

msgid "No ``JOIN``"
msgstr "No ``JOIN``"

msgid "No ``GROUP BY``"
msgstr "No ``GROUP BY``"

msgid "No ``SQL_CALC_FOUND_ROWS``"
msgstr "No ``SQL_CALC_FOUND_ROWS``"

msgid "With ``LIMIT``"
msgstr "With ``LIMIT``"

msgid ""
":doc:`/tutorial/storage`: ``ORDER BY`` clause has only columns or ``MATCH "
"AGAINST`` that is used in ``WHERE`` clause."
msgstr ""
":doc:`/tutorial/storage`: ``ORDER BY`` clause has only columns or ``MATCH "
"AGAINST`` that is used in ``WHERE`` clause."

msgid ""
":doc:`/tutorial/wrapper`: ``ORDER BY`` clause has only primary column or "
"``MATCH AGAINST`` that is used in ``WHERE`` clause."
msgstr ""
":doc:`/tutorial/wrapper`: ``ORDER BY`` clause has only primary column or "
"``MATCH AGAINST`` that is used in ``WHERE`` clause."
