Translation status

934 Strings 5%
Browse Translate
15,581 Words 5%

Strings status

934
All strings — 15,581 words Browse Translate Zen
56
Translated strings — 896 words Browse Translate Zen
878
Unfinished strings — 14,685 words Browse Translate Zen
867
Untranslated strings — 14,127 words Browse Translate Zen
11
Strings marked for edit — 558 words Browse Translate Zen
878
Unfinished strings without suggestions — 14,685 words Browse Translate Zen
13
Strings with any failing checks — 159 words Browse Translate Zen
10
Translated strings with any failing checks — 84 words Browse Translate Zen
5
Failing check: Unchanged translation — 62 words Browse Translate Zen
1
Failing check: Trailing newline — 12 words Browse Translate Zen
1
Failing check: Mismatched full stop — 17 words Browse Translate Zen
1
Failing check: Mismatched semicolon — 12 words Browse Translate Zen
1
Failing check: Inconsistent — 2 words Browse Translate Zen
4
Failing check: Reused translation — 5 words Browse Translate Zen
2
Failing check: Mismatching line breaks — 73 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Documentation: reference/reference_lua/compat/compat_tutorial 0% 36 731 6,164 36 0 0 0
Documentation: concepts/sharding/vshard_architecture 98% 2 42 293 0 3 0 0
Documentation: concepts/replication/repl_reseed 0 0 0 0 0 0 0
Documentation: concepts/engines/memtx 91% 4 287 1,990 0 0 0 0
Documentation: reference/reference_lua/datetime/interval_arithm 0% 29 320 2,155 29 0 0 0
Documentation: concepts/engines/vinyl 99% 1 114 735 0 13 0 0
Documentation: concepts/engines/index 0 0 0 0 0 0 0
Documentation: concepts/sharding/index 90% 1 1 8 1 1 0 0
Documentation: concepts/index 0% 37 581 4,495 37 0 0 0
Documentation: concepts/engines/memtx_vinyl_diff 0 0 0 0 3 0 0
Browse all components

Overview

Project website www.tarantool.io/en/doc/latest
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:tarantool/doc.git
Repository branch test-weblate
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-referencereference_sqlsql-features/
File mask locale/*/LC_MESSAGES/reference/reference_sql/sql_statements_and_clauses.po
Translation file Download locale/ru/LC_MESSAGES/reference/reference_sql/sql_statements_and_clauses.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 934 15,581 102,529
Translated 5% 56 5% 896 5% 5,792
Needs editing 1% 11 3% 558 3% 3,790
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 13 1% 159 1% 1,214
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 92% 867 90% 14,127 90% 92,947
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 936 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

15,581
Hosted words
934
Hosted strings
5%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+5%
—
Contributors
—
User avatar None

New strings to translate

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

878 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

File locale/ru/LC_MESSAGES/reference/reference_sql/sql_statements_and_clauses.po was added. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

Starting in Tarantool 2.10, if a parameter for an :ref:`aggregate function <sql_aggregate>` or a :ref:`built-in scalar SQL function <sql_functions>` is one of the ``extra-parameters`` that can appear in :ref:`box.execute(...[,extra-parameters]) <box-sql_box_execute>` requests, default data type is calculated thus: |br| * When there is only one possible data type, it is default. |br| Example: ``box.execute([[SELECT TYPEOF(LOWER(?));]],{x})`` is 'string'. |br| * When possible data types are INTEGER or DOUBLE or DECIMAL, DECIMAL is default. |br| Example: ``box.execute([[SELECT TYPEOF(AVG(?));]],{x})`` is 'decimal'. |br| * When possible data types are STRING or VARBINARY, STRING is default. |br| Example: ``box.execute([[SELECT TYPEOF(LENGTH(?));]],{x})`` is 'string'. |br| * When possible data types are any other scalar data type, SCALAR is default. |br| Example: ``box.execute([[SELECT TYPEOF(GREATEST(?,5));]],{x})`` is 'scalar'. |br| * When possible data type is a non-scalar data type, such as ARRAY, result is undefined. |br| * Otherwise, there is no default. |br| Example: ``box.execute([[SELECT TYPEOF(LIKELY(?));]],{x})`` is the name of one of the primitive data types.
Начиная с Tarantool 2.10 действует следующее поведение. Если параметр :ref:`агрегатной функции <sql_aggregate>` или :ref:`встроенных функций SQL для scalar <sql_functions>` --- один из дополнительных параметров ``extra-parameters``, которые могут появляться в запросах :ref:`box.execute(...[,extra-parameters]) <box-sql_box_execute>`, тип данных по умолчанию определяется следующим образом: |br| * Если возможен только один тип данных, он используется по умолчанию. |br| Пример: ``box.execute([[SELECT TYPEOF(LOWER(?));]],{x})``, тип --- ``'string'``. |br| * Если возможные типы данных --- INTEGER, DOUBLE или DECIMAL, по умолчанию используется DECIMAL. |br| Пример: ``box.execute([[SELECT TYPEOF(AVG(?));]],{x})``, тип --- ``'decimal'``. |br| * Если возможные типы данных --- STRING или VARBINARY, по умолчанию используется STRING. |br| Пример: ``box.execute([[SELECT TYPEOF(LENGTH(?));]],{x})``, тип --- ``'string'``. |br| * Если возможны любые другие скалярные типы данных, по умолчанию используется SCALAR. |br| Пример: ``box.execute([[SELECT TYPEOF(GREATEST(?,5));]],{x})``, тип --- ``'scalar'``. |br| * Для всех остальных случаев значения по умолчанию нет. |br| Пример: ``box.execute([[SELECT TYPEOF(LIKELY(?));]],{x})`` --- имя одного из примитивных типов данных.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

Default function parameters
Параметры функций по умолчанию
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

Example with Russian and Ukrainian and Kyrgyz collations: |br| Knowing that Russian collation is practically the same as Unicode default, |br| and knowing that the two-letter codes for Ukrainian and Kyrgyz are 'uk' and 'ky', |br| and knowing that in Russian (but not Ukrainian) 'Г' = 'Ґ' with strength=primary, |br| and knowing that in Russian (but not Kyrgyz) 'Е' = 'Ё' with strength=primary, |br| the three SELECT statements here will return results in three different orders: |br| ``CREATE TABLE things (remark STRING PRIMARY KEY);`` |br| ``INSERT INTO things VALUES ('Е2'), ('Ё1');`` |br| ``INSERT INTO things VALUES ('Г2'), ('Ґ1');`` |br| ``SELECT remark FROM things ORDER BY remark COLLATE "unicode";`` |br| ``SELECT remark FROM things ORDER BY remark COLLATE "unicode_uk_s1";`` |br| ``SELECT remark FROM things ORDER BY remark COLLATE "unicode_ky_s1";``
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

Example with Swedish collation: |br| Knowing that "sv" is the two-letter code for Swedish, |br| and knowing that "s1" means strength = 1, |br| and seeing with ``PRAGMA collation_list;`` that there is a collation named unicode_sv_s1, |br| check whether two strings are equal according to Swedish rules (yes they are): |br| ``SELECT 'ÄÄ' = 'ĘĘ' COLLATE "unicode_sv_s1";``
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

:ref:`EXPLAIN <sql_explain>` will not show the name of what collation was used, but will show the collation's characteristics.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

However, for searches and sometimes for sorting, the collation may be an index's collation, so all non-index ``COLLATE`` clauses are ignored.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

In other words, to pick a collation, Tarantool uses: |br| the first ``COLLATE`` clause in an expression if it was specified, |br| else the column's ``COLLATE`` clause if it was specified, |br| else ``"binary"``.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — Russian

In an expression with more than one ``COLLATE`` clause, if the collation names differ, there is an error: "Illegal mix of collations". In an expression with no ``COLLATE`` clauses, literals have collation ``"binary"``, columns have the collation specified by ``CREATE TABLE``.
 
a year ago
Browse all translation changes