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 Not available
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 100% 934 100% 15,581 100% 102,529
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 934 100% 15,581 100% 102,529
Failing checks 6% 58 12% 1,878 12% 12,773
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
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 934 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

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

Trends of last 30 days

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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

Default function parameters
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

: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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

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
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

In an expression, ``COLLATE`` is an operator with higher precedence than anything except ``~``. This is fine because there are no other useful operators except ``||`` and comparison. After ``||``, collation is preserved.
a year ago
User avatar None

New source string

testing_project / Documentation: reference/reference_sql/sql_statements_and_clauses — English

If one says ``COLLATE "binary"``, this is equivalent to asking for what is sometimes called "code point order" because, if the contents are in the UTF-8 character set, characters with larger code points will appear after characters with lower code points.
a year ago
Browse all translation changes