Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 58 0 0
Russian 5% 878 14,685 96,737 867 13 0 0
Please sign in to see the alerts.

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

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,868 31,162 205,058
Source 934 15,581 102,529
Translated 52% 990 52% 16,477 52% 108,321
Needs editing 1% 11 1% 558 1% 3,790
Read-only 50% 934 50% 15,581 50% 102,529
Failing checks 3% 71 6% 2,037 6% 13,987
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 46% 867 45% 14,127 45% 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 1,871 changes 1 change 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

31,162
Hosted words
1,868
Hosted strings
52%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New alert

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses

Component seems unused. 4 months ago
User avatar None

Component unlocked

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses

Fixing an alert automatically unlocked the component. a year ago
User avatar None

New alert

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses

Broken project website URL a year ago
User avatar None

Component locked

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses

The component was automatically locked because of an alert. a year ago
User avatar None

New alert

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses

Could not update the repository. a year ago
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
Browse all component changes