Skip to content

Commit d77a98d

Browse files
Onvemberactions-user
authored andcommitted
Update translation sources
1 parent 6b8d7ca commit d77a98d

File tree

2 files changed

+34
-1
lines changed

2 files changed

+34
-1
lines changed

locale/en/reference/reference_lua/box_space/create_index.pot

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -437,6 +437,9 @@ msgstr ""
437437
msgid "Allowing null for an indexed key"
438438
msgstr ""
439439

440+
msgid "is_nullable parts option"
441+
msgstr ""
442+
440443
msgid "If the index type is TREE, and the index is not the primary index, then the ``parts={...}`` clause may include ``is_nullable=true`` or ``is_nullable=false`` (the default)."
441444
msgstr ""
442445

@@ -449,6 +452,36 @@ msgstr ""
449452
msgid "It is legal to create multiple indexes for the same field with different ``is_nullable`` values, or to call :doc:`/reference/reference_lua/box_space/format` with a different ``is_nullable`` value from what is used for an index. When there is a contradiction, the rule is: null is illegal unless ``is_nullable=true`` for every index and for the space format."
450453
msgstr ""
451454

455+
msgid "exclude_null parts option"
456+
msgstr ""
457+
458+
msgid "Since version 2.8.2 an index part definition may include option ``exclude_null``, which allows an index to skip tuples with null at this part."
459+
msgstr ""
460+
461+
msgid "By default, the option is set to ``false``. When ``exclude_null`` is turned on, the ``is_nullable=true`` option will be set automatically. It can't be used for the primary key. This option can be changed dynamically: in this case the index is rebuilt."
462+
msgstr ""
463+
464+
msgid "Such indexes do not store filtered tuples at all, so indexing can be done faster."
465+
msgstr ""
466+
467+
msgid "``exclude_null`` and ``is_nullable`` are connected, so this table describes the result of combining them:"
468+
msgstr ""
469+
470+
msgid "**exclude_null/is_nullable**"
471+
msgstr ""
472+
473+
msgid "**false**"
474+
msgstr ""
475+
476+
msgid "**true**"
477+
msgstr ""
478+
479+
msgid "ok"
480+
msgstr ""
481+
482+
msgid "not allowed"
483+
msgstr ""
484+
452485
msgid "Creating an index using field names instead of field numbers"
453486
msgstr ""
454487

locale/en/reference/reference_sql/sql_statements_and_clauses.pot

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2047,7 +2047,7 @@ msgstr ""
20472047
msgid "In this case the search for 'a' will be done via a search of the whole table, what is sometimes called a \"full table scan\", even if there is an index for ``column1``."
20482048
msgstr ""
20492049

2050-
msgid "Ordinarily Tarantool chooses the appropriate index or lookup method depending on a complex set of \"optimizer\" rules; the INDEXED BY clause overrides the optimizer choice."
2050+
msgid "Ordinarily Tarantool chooses the appropriate index or lookup method depending on a complex set of \"optimizer\" rules; the INDEXED BY clause overrides the optimizer choice. If the index was defined with the :ref:`exclude_null <box_space-is_nullable>` parts option, it will only be used if the user specifies it."
20512051
msgstr ""
20522052

20532053
msgid "Suppose a table has two columns:"

0 commit comments

Comments
 (0)